Comments
-
I think I scribbled something out for REST once as well.
-
Edit the project's issue type scheme, removing all but "bug" (you may find it quicker to create a new scheme with just "bug" and swap over to it)
-
Yep, see https://confluence.atlassian.com/doc/configuring-secure-administrator-sessions-218269595.html
-
Go to Admin -> Issues -> Custom fields and read the list, looking for the word "locked". I'm curious as to why you ask (because it's useless information for anyone other than the current admin checking no-one has messed up the config by hacking the database), and why you didn't already know that was the answer.
-
There are two ways to get that behaviour from Jira 1) You have a custom resolution field, and are ignoring the system one (the gadget uses the system one) 2) Someone has hacked the gadget Jira is not selecting your results by system resolution, it just looks at empty vs not-empty.
-
Create two "field configurations", FC1 and FC2. Create one "field configuraiton scheme" that maps FC1 on to WorkerVacation, and FC2 on to EmployeeVaction Apply to the project Go into FC2 and flip "Top Management" over to mandatory
-
That looks right to me. I can see field names, and their selections. One cascading, two select lists.
-
I can't think of any other way to remove the panel, other than have no sub-tasks (in which case the panel is hidden until the first one is created) I think we'd like to see an issue that demonstrably has sub-tasks viewed through some other route and then the display where the panel is missing.
-
I think you are mixing up Status and Resolution. These are two totally independent things (technically independent. In real life, humans consider them together) These gadgets work, like most of the rest of Jira on a simple concept - "Issue is done when the resolution is set". Status is utterly irrelevant, you can have…
-
They are whatever you told it when you installed it.
-
If you think it's important, have a look at https://jira.atlassian.com - that contains all the feature requests. The community here generates some, and discusses them, but has zero weight when it comes to prioritisation. You should find the request and vote for it - that's the main input Atlassian use from customers.
-
The Core version will matter a bit - there's a range of JSU versions that work for the various versions of Core. But, your licence for Core + JSU is valid for all of them (up to the date of expiry). And, the universal plugin manager will handle all of it for you, only installing valid versions! (Admin -> Apps) There is no…
-
That's fine, but I think you have to understand that software can't do everything. I'm not an Atlassian, and I'm not saying this is something I would not want to do if I were. But I've got a list of things I would like Jira to do, and this is the sort of thing that is very very low down it, as you say, because it doesn't…
-
I can see that thread (I remember I got stuck on it because there is nothing in Confluence that would do this. It has to be something with the persistent file system)
-
That will only happen if you are moving the issue to a new project as well as changing the type (If you move inside the same project and the workflows are the same, the status won't change, if they are different and the current status not in the new workflow, it will ask). You should not be moving issues as a matter of…
-
That would only lead you to a small number of edge-cases though.
-
If it's a common operation, you have a bit of a problem with your users. Might be worth fixing the problem at source.
-
They're not "done" unless they're in the right hand column on the board. You could deselect them in the board filter, but then you will have no way to get them into the done column from the board, you'll need to open each in plain Jira and transition it. Doing a release is the correct way to clean out the "done" column.…
-
Bear in mind that although it'll get a consistent database, you need to think about how to snapshot the attachments too (and the rest of the system if you're doing a more active fail-over type thing)
-
Have you added a location map custom field?
-
It's not. It's using the one I've pointed to.
-
I think you'll really struggle with videos - Atlassian tend to release so fast, videos could be obsolete within days of being made. They tend to be focussed and generally useless at informing admins as well. What you need is the more generalised training and background stuff you can find in Danny's links, and to actually…
-
The only time help -> about won't show you the version is if 1. Your admins have hacked it out (unlikely, as there's no good reason) 2. You are on Cloud Jira, so the version is irrelevant because it's Cloud
-
Ok, that should give you some access to select fields for your project, but you still can't add types or new fields.
-
What is the difference between the settings for the two fields?
-
Ok, that's not in the original question, so there was no way to know. It is easier in some ways, as you can move an issue if it's not the issue being transitioned, but your code will still need to think about ensuring your "clone" is complete before trying the move. The comments about moving issues still stands though -…
-
You have to make assumptions based on your business logic. For example (and this is a real one I wrote listeners for, although I've simplified) * Event: Team Tour Amsterdam * Event has a multi-user select field "attendees" * Listener creates sub-tasks like this:* Sub-task: Hotel for Eliza * Sub-task: Hotel for Nic *…
-
A default priority can be set in the priority scheme. If you wish to change existing priorities, make sure you have the "bulk edit" permission, search for the issues to update, and use bulk edit to change the priority.
-
Up to Jira 7.6, you need to be an administrator to add fields to your project. From 7.7, you need to be a project administrator with the "advanced configuration" permission set in the permissions scheme To create new issue types and new fields, you need to be a Jira or System administrator
-
1) You are going to need to write an add-on to do that. ScriptRunner can do things like scripted fields and data manipulation, but that behaviour is going to need a full-on new field for it. (You could get most of it by simply dropping the field and using a standard issue link) 2) ScriptRunner could do that, if you…