we have a service desk set up for quite some time and recently I have noticed that the resolution "Unresolved" is not working properly. Or maybe it is working but... I can see the "Unresolved" status via the Issue view, however when I want to filter all issues with unresolved status from this specific service desk all the issues are not visible except for 11 of them.
Btw the "Unresolved" resolution status is the one in Italic (System) and not part of the Resolutions list in the Administration section.
I am not able to find similar cases and I am thinking about a specific "Unresolved" resolution status to be added into the Resolutions list so Jira would acknowledge the "Unresolved" status for the filters. Unfortunately I cannot validate if this is the best idea. What do you think? Could you please suggest any other suitable solution? :)
Your question is mixing up status and resolution (this is not uncommon), but you are also suggesting making a terrible terrible mistake as well.
Note that these two have no logical connection, nor one in the code. You can have issues in status that suggest "done" with an empty resolution, so they're not done, and vice versa.
In almost all places, Jira considers the resolution to be the thing that determines resolved or not. Status is only looked at on Scrum and Kanban boards.
A good design is to set the resolution on any transition from a to-do/in-progress status into an end status and clear it if going in the opposite direction. Some jira project types will do this automatically by default, but if you do mess with a workflow, you should bear it in mind.
The mistake not to make is adding "unresolved" to the list of resolutions. This would allow you to show issues as having a resolution of unresolved, meaning they are resolved. This is of course, complete nonsense. You should never have a resolution that suggests an issue is not resolved, the resolution field being filled with anythig means the issue is resolved.
Jira displays the italicised unresolved when the field is completely empty. It's putting something in front of us humans so we don't ask why there's nothing there.
So, to fix your problem here, you just need to correct your workflow, making resolution follow status, then re-open and re-close your issues (or script an automated fix for the end-status-but-but-no-resolution status)
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events