Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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.

Atlassian Community about banner
4,463,207
Community Members
 
Community Events
176
Community Groups

How to show the subtasks in Kanban board but hide them in Roadmap?

My team is trying to move from Sprint board into Kanban board. While working in Sprint board, we worked with subtasks to break down the story into smaller pieces. Now after changing our board into Kanban, we noticed these subtasks are also listed in the Backlog. This is really annoying as it clutters the roadmap. On top of that, since the parent story can have different status compared to its subtasks, it makes the roadmap looked even worse. If I exclude the subtasks using the filter, the Backlog will look fine, but then I will lose the subtasks in the Kanban board. How can I achieve a middle ground where I want to see the subtasks in the Kanban board but hide them in the Backlog?

TLDR: Work with Kanban board. How to have subtasks in Kanban board but hide them in the Backlog? 

 

Thanks!

1 answer

0 votes

You can't really do this with Kanban.

Kanban does not care about issue levels - your backlog is a stream of cards, and each one is an item that needs doing.  It does not care whether they are Epics, Initiatives, Themes, Issues, or Sub-tasks - a card is a card.

If you're going for a Kanban approach, you have to work out how best to work with "each card needs some attention, separately"

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events