Hello friends! I am having trouble creating a filter that sorts items with a Label solely based on its Status. The issue is that the sorting is being done first on Project Key, which is then further sorted by Status, so there is a stagger between statuses divided by different projects. The desired end result is to group all items of the same status together regardless of the project the item belongs to.
For example, we have roughly 6 projects that have items with the "Security" label. By running the attached JQL query, all items throughout all of our projects that have the "Security" label are returned and sorted, but are sorted first by project key, and within each of those project clusters they are then sorted by Status. Is there a specific attribute that we can add to the query to properly sort this filter?
Hi @Chris Honda
(answering in a new thread to not interfere your conversation with John)
I could reproduce this on my site. What I believe is happening here is that your projects use different workflows, and thus different "status entities", even if these statuses have the same name and "look" the same. Jira (or more specifically, JQL), for some reason, then sorts them in this particular way.
What you could try is to sort also by status category; perhaps this would give you a more intuitive outcome.
... and just to put this out there: The status order is handled correctly (in the sense of: like what you would expect) in the app that my team is working on, JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that allows, among many other things, viewing, inline-editing, sorting and filtering by all your issue fields - of course including the status. This is how it looks in action:
JXL integrates into the project sidebar, so many of our customers use it as a "supercharged" addition to the native search view.
(Note that while JXL is listed for Cloud and DC only at the Marketplace, it works perfectly fine with Server, too. If you'd like to try JXL, I'm happy to create a free trial license for you.)
Best,
- Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Hannes,
Thank you so much for your response and research into this issue! We're currently testing your recommendation of sorting by status category, and we're also looking at the JXL app as well :) I'll reach back out and let you know if the team wants to proceed with the trial license, it looks great to me so far!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chris - Welcome to the Atlassian Community!
This looks strange because it doesn't look like it is sorting by Status at all. What types of projects are these?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey John, thanks for the warm welcome!
We have a variety of project types, all of which are company-managed. Most of them are Project Management projects, with a few Task Management projects also holding tickets with the applicable Label.
Now that you mention it, there doesn't seem to be much sorting going on. I'll try creating the filter from scratch to see if I can get basic sorting to happen.
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.
Sorry for all questions, but this definitely has me baffled. Where are you doing the query/filter? Just in the Advanced Search function?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No need to apologize John, I greatly appreciate your help and expertise with this issue! We tried submitting a JQL query in the Advanced Search bar and clicking on the Status column highlighted in conjunction with the dropdown to filter for the desired label (some screenshots of our updated search criteria included).
I agree that this is quite confusing :) I can see some use cases where JQL would include the Key as a parameter for most sorting activity, and putting that aside it seems as though the sort param we submit is overridden and grouped by Key first.
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.