which value can I add to Resolution field, if I w ant it to be empty by default ? (= unresolved) I think JIRA ships with value Fixed as default. But that s disturbing since a task i just created, c ant be already fixed ?
You can't leave it "empty by default". What Rahul is getting at is that if you put the field on a screen for create or edit, then it will take a value, and hence the issue will appear closed. Remove it from your create/edit screen if you've added it there.
You should only put the resolution field on transition screens, and only on transitions that go from a status you want to think of as "open" to status that you see as "closed".
No, there should be NO "unresolved" type resolutions on the list of resolutions. If there are any, then remove them, as they're wrong.
This is a case where the technical explanation is actually helpful... JIRA regards the resolution field as a flag to see if an issue needs any attention.
In the database, the field for any issue can either be empty (null), or it will be holding a value (From the list of resolutions).
If the field is "null", JIRA treats the issue as "something needs doing", and it shows that by displaying "unresolved".
If the field has anything in it, then the issue is "resolved", and it displays the value from the resolution field, and displays the strikeout on the id in some places, and ignores it in some reports etc.
Some inexperienced admins make the terrible mistake of adding words like "unresolved" or "none" or "open" to the list, thereby breaking it - there is something in field, so the issue is resolved. Doesn't matter that it says "open", the field has a value, so the issue is resolved.
It'd be great if JIRA's engineering team could look to improve that. That implementation led to a terrible user experience where one needs to RTFM to understand how to deal with Resolution = Unresolved properly. One can imagine several other implementations that would have avoided the problems listed above and given the user a much more intuitive experience.
I'm one of these: Some inexperienced admins make the terrible mistake of adding words like "unresolved" or "none" or "open" to the list, thereby breaking it - there is something in field, so the issue is resolved. Doesn't matter that it says "open", the field has a value, so the issue is resolved.
Where can i remove the resolution field that i've allowed them to edit?
Ok, you'll need an admin account.
First, if you've got none/open/unresolved resolutions, rename them to something like "do not use me". Nip into Admin -> Issues -> Resolutions and rename them.
Now scan the volume of the problem. You need to search for "resolution in (list of broken resolutions". Save that filter and give it a sane name. You'll probably want to use it in a couple of dashboard gadgets to help you identify issues that need updates.
The main thing to check is the status of each "resolved but broken" issue. If they are all in status that means done/ended/closed/whatever, then you can skip the next step.
If you have issues with broken resolutions and they are "open" type status, then you need to get the resolution cleared out. You can't edit it away, you have to push the issues through transitions with "clear resolution" on them - usually "reopen issue" transtions. I usually end up editing workflows to add in "go back to same status, but clear resolution" transitions to do that, or using the script built into the Script Runner add-on.
Once you are in a state where you have no issues with bad resolutions that are in an open status, you can simply delete the bad resolution - JIRA will ask what you want to swap the resolution to.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot