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; } } }

Is the Priority field disabled by default in Jira Agile?

Andrew Cohen

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!

Accepted answers

Peter T

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.

All comments

Peter T

Andrew Cohen

It looks like the Agile thinking is that rank should be used instead of priority. Would be curious if others agree?

Andrew Cohen

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.

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

jira-administration