As I try to delete it says:
Delete Resolution: Unresolved
Confirm that you want to delete this resolution, and specify what is to be done with the issues currently attached to it.
There are currently 167 matching issues, that must be changed to another resolution.
|New resolution for matching issues
You really do NOT want a Resolution called "unresolved".
The reason is simple - Jira considers the Resolution field to be the "open or closed" flag. If the field contains any data, the issue is "closed". It does not care if the data says "unresolved", "open", "penguin", "closed", "anvil" - the issue is closed because the field is set.
This makes resolutions with names like "unresolved" or "not done yet" or "open" an absolute nightmare for the humans because they see "unresolved" whereas Jira sees the issue as "resolved"
In other words, delete "unresolved" now. It's making your data complete nonsense. (167 issues is a minor change, you don't need script runners or anything complex, just delete it)
Ah, I see. Sorry.
You can't select the "empty" option when doing this. The assumption is that resolved issues would stay resolved and you're only removing the resolution because it needs changing to another.
You'll need to bulk-edit the issues to remove the resolution before deleting it. 167 is only a small set though.
Also try a debugging test by specifying the user directly. If you were logged in as me for example, then try "assignee = currentUser()" and "assignee = nic", and a third test of "assignee = nic" when logged in as someone else.
The numbers you get out of those might tell you more about the problem.
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