On what basis do the issue cards form sequence under the To-Do column on the Kanban board?

Ayush Mishra May 30, 2022

I cannot determine the basis on which the issue cards get sequenced whenever a new card is added to the sprint. The sequence order under 'To-Do' on Kanban/Active Sprint board is shown on the basis of Date Created, Priority, or something else?

 

Also, what is the process of changing the sequence automatically without dragging and dropping issue cards?

 

Just want to confirm that if we add story points to issue cards, the card with the highest story points would appear on top?

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2022

It's sorted by whatever sort order you have used for the board.

In most cases, this will be the rank, but you might have changed it to something else.  If you have, you might struggle a bit - sorting by priority for example will add Jira's "best guess" into your board.  Imagine you have 3 possible priorities and 30 issues - unless you specify another sort criteria, Jira can't know what order to place the 14 issues all on "trivial" in, so it falls back on a simple "lowest id in the database is the oldest, so it's the highest within all the trivial issues"

To automatically change the "sequence", you need to look at the query the board is using, and either fit your input data into it, or automate something to change it.

You could indeed order by story points, but I would suggest that this would be pretty much useless to your team.  If you went high to low, every sprint would automatically take the largest piece of work that needs doing, not the one that needs doing the most.  If you went low to high, every sprint would be filled with trivial-to-do pieces of work and you'd never get to start on big projects.  If you're using Kanban, you'd just end up doing oldest first (becausee your estimates are irrelevant to Kanban, and Jira would fall back on age)

Ayush Mishra June 1, 2022

Thanks, Nic! This was really helpful in understanding. Appreciate it. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events