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

Changing a sub-task priority from different story in the same colunm

Felipe Beray

Hello you all.

We have a kanban board in Jira with some colunms. In a colunm we have grouped two different status. When we try to invert the issues order, we are not being able to do it. They are sub-tasks from different stories at the same colunm, but we would like to bring some of them to the top of the list.

Have anybody faced the same problem? Is it possible to solve anyhow?

Cheers

Comments

Jack Brickey

Hi @Felipe Beray , welcome to the Community.

it seems that you have two or more statuses mapped to a single column in your Kanban board and wish to chang the order of this statuses. Unfortunately, this is not possible. Well, there is a way but I doubt you would want to do so. The order of the statuses has to do with the order that they are created. Each status has an underlying ID and that ID is used in any kind of ordering. So you could start over and rebuild your workflows from scratch, and be careful about the order in which you create your statuses. However, this is a very unattractive approach.

One other thing, if you are speaking of ordering the issues within the status itself, that would be handled via the ranking assuming you have ranking enabled on your board.

Felipe Beray

Thanks @Jack Brickey

but not actually change the order of the statuses, it would be change the order of the cards with the same issue type and statuses

Does it apply also on what you mentioned above?

And for sure, start from scratch all over again is not in the game

Johnny FromCanada

IME, Jira Subtasks are quite limiting, and can even encourage various team dysfunctions.

One alternative is to stop using them, and instead install one of the free “checklist” plugins from the Atlassian marketplace.

Each issue can have its own checklist. The team’s tasks from “How” planning can be captured and tracked there (contained within the issue itself).

You can set up a default checklist template for each issue type, which can help for things like Definition of Done criteria.

Gracjan Wesołowski _HeroCoders_

Hi, @Felipe Beray

totally agree with @Johnny FromCanada .

The checklist is a powerful, but lightweight way to manage small tasks, track your acceptance criteria, and ensure completed stories meet the definition of done.

They have many useful functionalities, for example, our app, Issue Checklist Free allows you to add deadlines, and assign/mention users for each Checklist item. Also if you are using kanban boards, you are able to show checklist progress on them.

The configuration is quite easy, and if you have any questions we are happy to help.

Best Regards,

Gracjan

Jack Brickey

Ordering is generally done by ranking. Could you share your board's filter? I'm

Felipe Beray

but then we would brake our metrics by doing that, wouldn't we?

Johnny FromCanada

IMO, from a Lean-Agile perspective, metrics at a subtask level will likely lead to local optimization, and to Team dysfunction.