Comments
-
Yes, there's a few that do scripted fields, and the response might be different for each App. When you defined this field, did you tell Jira it was a number field, or something else (string etc)?
-
You'll need to read the log file to find out where the problem is.
-
What App is providing scripted fields?
-
They will eventually go out of support, leaving you with no way to ask Atlassian for help (although you can still ask, and they do try, they will often simply tell you "upgrade"). There will be no patches or security updates. Everything will continue to work as it does now, and when you do decide to upgrade, you'll come…
-
The scheduler runs the export using memory and temporary files, when the export is complete, the finished file is copied to the backup directory and the temporary files discarded.
-
That's probably authentication, as you suspect. Start with a look at https://developer.atlassian.com/cloud/jira/platform/jira-rest-api-basic-authentication/ for that. It covers the "basic" option, which I tend to stay away from apart from getting started with a bit of code, but there's links to the other options in the…
-
We don't know what docs you are following, or where they are not "a conclusive guide" already!
-
You can't upgrade Jira Core (which is the platform the other two run on) from inside the application, because it is structural. It would be a bit like trying to rebuild the foundations of a house while the house is still there. To upgrade Jira Core, you can run the installer for the version you want (it is ok to go from…
-
I don't quite understand the question, but see the doc I pointed to for an explanation of the three parts of the url I said how to build.
-
I'm afraid you have destroyed your installation. Just copying bits from other installations is not going to be good enough. Your best option is to install a new clean copy of Jira, of exactly the same version, then import the data from the backup you took at the beginning of the process.
-
It means you need to unpack the install files you got in step 2.
-
I suspect it's more a case of why would they change a standard and basic report that works for most users when users who need something slightly different can run their own version.
-
They are whatever user and password you have set up in Jira to do this integration with.
-
This is what they have been designed to do. I'd recommend installing using the Jira Software installer, then adding Jira Service Desk to that install with "admin -> manage applications"
-
It is whatever you chose for the base-url for the system with /rest/api/latest added to it (then /issue/[key] for a specific issue) See https://developer.atlassian.com/server/jira/platform/rest-apis/ for a starter
-
That is what Ismael is telling you - there is no status or transition in your workflow, so you need to add one.
-
No, you will need an App to do this. Jira already does that sort of tagging in the email subject, so there's absolutely no need to put redundant information into the body of the email as well, as it's already there. To needlessly duplicate information already there, you're going to need code in Jira, which means an App. Or…
-
By default, the standard rank field is a global field. If you're using it as intended, then the only thing you need to do here is educate your users that it is global so that they don't mess it up. If a previous admin has added other ranking fields, you probably want to unpick that, going back to a single one.
-
Those drafts are stored as single pages in a sort of invisible space. Again, they'll not have any significant drag on your system. You need to look at the resources Synchrony has and what Confluence is doing that makes it slow.
-
Ah, hang on, that means "you can't add a status", not quite the same thing as "can't put a status into a column" If you can't add a status, then the workflow for the project(s) behind the board do not allow for project admins - they either need to be "simplified" or modified so that they are not shared across projects to…
-
Nonsense, it's not in the slightest bit absurd. Imagine two issues of the same type at two different points in the flow. Your "per project endpoint" suddenly becomes useless as it has to cover every single transition possible across everything.
-
Ok, so as I said, the issue security scheme is hiding it.
-
Synchrony doesn't look at the history, it is something else. Has it got enough resources?
-
Ah, ok, well, butchering your page history is not going to fix any of these (well, the clean up, arguable, but as the history isn't reported on, it's still not going to do much)
-
Are you a board admin as well? Also, what is the behaviour for "can't"? Error message, warning, can't pick up a status, just jumps back to where it was, etc?
-
No. As I said. Your best option is a validator. You could also muck around with javascript, or better, Behaviours from Scriptrunner, but these can easily be bypassed if people feel like it and will be completely ignored by certain add-ons and automations.
-
It depends. If you want to run them as a single team, with a single board and velocity, then you're going to have to analyse the time in status, and essentially beat up the QC part of your team - they're underperforming and need help with that (often, more resource, but not always) The other option takes the blame off the…
-
That is not what your original question asked. You can transition other issues in a post-function, you don't need the fast-track - that is only for the current function.
-
They are Cloud only, for the foreseeable future.
-
What do you mean by "admin console bar"? If you mean the menus, then you don't get create if you have not got any permission to create any issues.