It looks like we use the standard "Agile Field Configuration" for our fields, which does not include the Priority field. Before I ask my admin to enable this field, is there a reason why Priority is not used in Agile? Or is this just our custom implementation?
Thanks!
In Agile world the alternative of priority is called Ranking and this is what JIRA Agile is using. Having both with be very confusing and without ranking the order of the stories on the planning view won't work.
I appreciate that but oddly enough the Agile Sprint Healthcheck Gadget shows a count of Blockers, which it defines as those issues having a Priority = 1, which is pretty weird if you are not supposed to use priority for Agile Sprints.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It looks like the Agile thinking is that rank should be used instead of priority. Would be curious if others agree?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Earning the Mindful Member badge proves you know how to lead with kindness, plus it enters you into a giveaway for exclusive Atlassian swag. Take the quiz, grab the badge, and comment on our announcement article to spread the good vibes!
Start here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.