nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Which field to use ranking Jira issues with multiple filters?

Jimmy Trivedi

This is my filter query:

assignee in (currentUser()) AND project = GJP AND issuetype in standardIssueTypes() AND status in ("In Review", Pending, Reopened, TODO, "Work in progress") AND labels in ("Default", Learning, Regular, Support, Transcation, Trending) ORDER BY due ASC, priority DESC

So, according to above query, 10 issues are coming in the list. 5 out of 10, which is coming on top of list and matching with ORDER BY. Because Due date and Priority are same for all 5 issues.

Now, my question: Out of 5 which has everything same [due date and priority], I want one more field, which even give more priority-ranking, and should indicate that that which one to complete first. like for example for all 5 issues, I want to give number 1,2,3,4,5. So that first I can complete number 1 issue, then 2 and so on...!

Can you please advise what should I do for that?

Accepted answers

All comments

Ste Wright

Hi @Jimmy Trivedi

You could use Rank ASC?

Rank ASC will order the Issues as they appear in your Board/Backlog, from highest to lowest. If the Issues are already in order on your Board - that could be a simple solution.

So your JQL might look like...

...ORDER BY due ASC, priority DESC, Rank ASC

I'd be careful with using number fields for prioritisation. These can get complicated - for example if you had 100 issues numbered 1-100, and then needed to add an Issue at 62, there's lots of other Issues you'd also need to edit!

To see more information about how Rank works across your wider Jira instance - see this help page: https://support.atlassian.com/jira-software-cloud/docs/rank-an-issue/

Ste

Jimmy Trivedi

Hi Thanks for the reply, but I'm not able to modify it, please check 3 screenshot. Screenshot 2023-01-22 at 19.23.12.png Screenshot 2023-01-22 at 19.24.53.png Screenshot 2023-01-22 at 19.25.12.png

Jimmy Trivedi

@Ste Wright Any update?

Nic Brough -Adaptavist-

The ranking is used in the backlog to do the click and drag to rearrange the order of the issues in your backlog.

You can not edit it directly, because Jira can't risk a human entering a duplicate value. It's generally not even displayed to us because it is not a human-friendly format.

Nevertheless, ranking is the best way to do what you want. The way I think of it is that "priority is a great piece of information to inform ranking, but it can not dictate it"

Jimmy Trivedi

I solved using Custom Jira field.

https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/

Nic Brough -Adaptavist-

That's not a "solution", that's creating an unneccessary botch

Jimmy Trivedi

@Nic Brough -Adaptavist- As per my requirement, your solution is not working.

You're saying that to use backlog, but I want to edit it from my issue itself, which I'm able to do it using custom field.
You're saying that I can not do human entering duplicate value, but for custom field I'm able to do it and give whatever number I want whether it's 1.5 or 2.5.

Nic Brough -Adaptavist-

Your solution can not work. Rank needs to be a unique identifier that places an issue between two others in an ordered list.

You can, of course, order issues by priority and (for want of a better word) sub-priority, but this will not work in your backlog, it misinforms people about the actual order, and it is of little use in reporting.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management