The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

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

marcel_alim
marcel_alim
December 7, 2022

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!

Watch
Like Be the first to like this
1080 views

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
Get recognized
December 7, 2022

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"

Reply
Jira
Jira
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security