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

Numeric Priority -KANBAN BOARD

Joao Borges_ch4uwn

Hi there, is there a way to list tickets in KANBAN board in a numeric way.

I am trying to organize the board at the moment and its hard to prioritize tickets just based on their place on each column. I would like to see a number next to it, so developers and dbas know which ticket to tackle first

Thanks

Accepted answers

All comments

Nic Brough -Adaptavist-

Numbering issues would have to be done by going from top to bottom through each row and column. The numbers wouldn't tell you anything more than where the card is on the board, which is what the board is already showing you.

The next ticket to tackle is the one at the top of the column that no-one else is working on.

Joao Borges_ch4uwn

But how could i number them ? I dont want to update the summary or the ticket title. Is there a way to put a number on each ticket on the current board ?

Nic Brough -Adaptavist-

You can't number the issues themselves. Not because you can't physically do it, but because it is not really of any use.

As soon as the board changes, you would have to re-number every issue.
And somehow store different numbers for each and every board.
And tell people what the different numbers need and somehow know which one(s) they are interested in
And explain what happens when a board is quick-filtered

I think what I'm getting at is that numbering an issue according to its board position is not as useful as it sounds at first.

You could number them visually on a board by injecting some javascript, but that number would not be on the issues, and could be totally different on an issue when its displayed on another board.

I'm a bit stuck on what problem you're trying to solve with numbering the issues like this. What's wrong with "the next one to tackle is the one at the top of the column". That's (partly) what ranking is for.

Joao Borges_ch4uwn

@Nic Brough -Adaptavist- Numbering will be for developers to know which ticket they need to finish first. But i do understand your point, " the next one to tackle is the one at the top of the column" . And yes, the numbers might be confusing and cause even more problems in the board. But I am trying to filter a swimlane to show priority tickets on top, but its not working

project = TECH AND component = "Business - New/Existing development" OR summary ~ business ORDER BY priority DESC

Whats wrong with the query ? Should i open a different question for it ?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software