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
Community Members
Community Events
Community Groups

How to exclude Scrum and Kanban Board Backlog Items in Advanced Roadmaps?


We're using the Advanced Roadmap for Company Wide Planning, meaning that in one plan we are able to see all team goals and progress. 

Some of these teams use Scrum Boards and some use Kanban Boards, and of course all are Company-managed projects.

However, in this Plan we only want to show Issues that are part of current and future sprints or are in the Kanban Board, so we want to exclude all Issues that are in the Backlog for both types of boards.

The Sprints Filter is not the solution since using this filter gives options to include a) active, b) completed, c) current or d) no sprints and all first three options will only show Issues that are part of Sprints and will exclude the Kanban Boards; whereas, the last option will include backlog items, hence the "no sprint".

Has anyone had a similar issue and found a work-around? 

Would be great if Advanced Roadmaps had this Filter option for the two types of Boards, Scrum and Kanban; as well as, an option to Filter by Date and/or Time Intervals.

2 answers

0 votes
Bharathi Rising Star Sep 09, 2022

Hi @Rrita Rugova

As @Trudy Claspill has rightly indicated, you can create a specific filter query to be used in Advanced roadmaps that will include the issues, both on the scrum and kanban sides, that you need to be filtered and listed on the roadmap.

0 votes

I think you could do this by making your Advanced Roadmap source a Saved Filter. You would have to construct a JQL that would retrieve all the issues from the relevant projects.

For projects using Scrum you could use the "sprint in openSprints()" criteria to retrieve issue in Active Sprint.

For Kanban it will be more challenging. If you have projects using different statuses for the Kanban backlogs you will have to map all of those as part of the saved filter.

This is assuming you are using only Company Managed projects. If you have Team Managed projects that use Kanban and the Backlog feature, there currently is no way to distinguish which issues are in the Backlog vs. on the board. Team Managed Kanban Backlogs are not based on the Status of an issue.

Suggest an answer

Log in or Sign up to answer