I expect the problem is that an inexperienced administrator has placed the "resolution" field on the "edit" screen for the issue type.
You'll need to get that removed to prevent any further issues being broken, then we can look at fixing the issues that have been broken.
Resolution should only ever be placed on transition screens. Never on edit.
Thank you Nic. that would be it.
The reason for placing the resolution field on the edit screen is that if we reopen a resolved case the case still shows as resolved and is not visible when using a show only unresolved cases by placing it on the edit screen it allows the resolution to be visible and changed easily.
>if we reopen a resolved case the case still shows as resolved
Your admin should place a post-function for "clear resolution" or "set resolution to <none>" on the re-open transition.
The resolution field is intended to capture a resolution when you resolve an issue. Because JIRA relies heavily on the resolution, it doesn't want to rely on the users to do it every time, so it uses a default in case the user forgets. That behaviour occurs on the edit screen, so you resolve issues just by editing them if the resolution is there.
It's a hangover from JIRA 1, vastly flawed, and my opinion is that "resolution filled = resolved" should have been sacked off in favour of perspective dependent meta-status years ago. But that's another essay.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs