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
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
The backlog and roadmap views in Jira Next Gen are great, but there seem to be incongruities in the handling of the classification as "backlog" and the status designation (To Do, In Progress, Done).
It doesn't make sense that anything in backlog would fit into the standard status designations of To Do, In Progress, Done. Anything in backlog should really have a separate status designation... for instance, a backlog issue could be assigned the status of "backlog" :)
I envision it working like this:
If backlog is turned on, new issues are created with the status of "backlog". These issues would be visible in the backlog section, and could be easily identified in roadmap view because of the "backlog" status (which solves the problem where currently, if you are in roadmap view you can't tell what is backlog and what is not). In board view there would be a new column at the left called "backlog" for the backlog issues.
Note that a solution like this would also address other related issues, like https://jira.atlassian.com/browse/JSWCLOUD-17471 (moving issues from backlog to board from the issue view), because "backlog" would be listed as a status choice.
Is there a workaround to accomplish this, or does this need to be a new feature implementation?