The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Any advantage to specifying Priority level for issues in the backlog?

Paras Patel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 16, 2020

I get the advantage of giving sub-tasks a priority level, even when they're in the backlog, but for issues I can't think of any. I haven't worked on any complex software projects using JIRA, but conceptually I would assume sprints aren't comprised of many issues (if this assumption is false, then yes I can see the advantage) and when moving issues into a sprint, you're following some pre-defined workflow rather than moving issues based on priority level. So what good does labeling issues in your backlog with a priority level do you? 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Joe Pitt
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 16, 2020

Priority would be a consideration of what to work on first. 

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events