The used filter counts issues with "NOT resolution = Unresolved" resolutions, but also issues with "resolution = Not Started" are counted.
I do not see the possibility of changing the count: the filter is hidden at the admin.
You say: The used filter counts issues with "NOT resolution = Unresolved" resolutions, but also issues with "resolution = Not Started" are counted.
Yes. The issues that have "resolution = Not Started" ARE resolved. You've told JIRA they are resolved.
Yes it is.
Let me put it this way. When you created the "not started" resolution, how did you tell JIRA that this resolution is not a resolution?
Answer is that you did not. Because it is a resolution.
When you set the resolution field on an issue to anything, the issue is resolved. It doesn't matter if you use the words "not resolved", "unresolved", "not done", "not started", or for that matter "penguin" or "arglefloop". You have put something in the field, so the issue is resolved.
That is the point. You don't.
If you set any resolution, you are telling JIRA the issue is resolved. The text you put in there is irrelevant. You need to leave the field empty on unresolved issues.
Your "not started" is a resolution, so the issues with it are resolved.
That's really strange. I looked at our service desk and the jql on the closed issues comes up as this:
reporter in organizationMembers("Test User Group") AND NOT resolution = Unresolved AND project = SUPTEST AND "Customer Request Type" is not EMPTY
What does yours look like?
...be more productive while being fun to use at the same time. For some, getting started can be a bit intimidating. This is especially true if Jira Service Desk is your first exposure to Atlassian...
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