Hi,
I'm having trouble removing tickets with the status of Closed from my JIRA queue filter.
resolution = Unresolved AND status != Closed
What am I doing wrong here?
I understand that the most proper way to handle this is to ensure that a proper resolution is attached to each ticket but that means going in and reopening and closing every ticket that was closed with this post function missing. It's not an option for us.
Surely I can do this using JQL??
Hi, @Ben Weisman !
If I correctly understand your problem, you have issues in status “Closed”, but some of them don’t have resolutions. So these issues staying on your boards.
Now you want to get these issues and transition them from “Closed” to “Closed”(itself) with post-function that will set the resolution.
Is it your case?)
To resolve it:
1. To create transition with post-function
2. To get that issues with JQL : project in (TEST) and status in (Closed) and resolution = Unresolved
3. To make bulk-transition (bulk-change)
Good luck 😉
Hey @Ben Weisman
So you want to show the items that are unresolved but are not in status closed?
That query should work then. Is it the whole query you are using?
In the long run you could automate or bulk edit the issues because your reporting will also be ‘broken’ like this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I just figured it out.
status != Closed AND resolution = Unresolved AND ("Request Type" = "Support - Retail Solutions" OR Product = "Data Owl/Retail Solutions") ORDER BY "Time to resolution" ASC
Does this make sense to you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.