Earn badges and make progress
You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Nextgen Kanban Board Ordering, Blocking and Hidden Status's
Looking for ideas from the Atlassian Community Brain Trust around whether I can do the below or if these items perhaps should be flagged for the Nextgen roadmap?.......or if I am just mad.....
1. Kanban columns auto prioritised by ticket priority (and perhaps status)
As we are progressing we are starting to see the Board fill across the different project roles. As the tickets roll out of backlog and onto the Board they are not always moved based on priority. Meaning we then get a jumbled mix of 1's, 2's and 3's (currently)
Looking to see if there is an option to be able to sort the columns by priority automatically to ensure all the critical tickets are always at the top and visible and so on and so forth. ?Perhaps even an option to rank Critical bugs over Critical Stories or Improvements? or ?perhaps it is the default sort order when an item gets added to the board but you can then manually move tickets to override if needed?.
Is there a way to do this as I cannot seem to find anything other than manually moving and managing the tickets.
2. Blocked field at the top of the Kanban board when flagged as impediment
I know on Classic Projects when an item gets flagged/blocked it can end up in its own section at the top of the Kanban Board so it is clear what is blocked and can be easily called out/worked on.
I cannot work out how to implement this on a Nextgen Project. Am I missing something or is it not there?
3. Won't Do Status in Workflow but not on Kanban Board
Finally, some of the tickets in the backlog by the time we get to them are either duplicated or no longer relevant or just not of business interest to be completed. Currently I can only see two options in a Nextgen Project. Complete it as Done with comments indicating it as a Won't Do or having a Won't Do column visible on the Board (but no way to flag this as a secondary resolution/end state).
Again is this just me missing something or is this not currently available on nextgen projects?