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

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


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.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Best practices (team) board filters in combination with advanced roadmaps

Our department recently started using agile. Currently 3 teams are working on their own “agile” island.
To move to “Program / team of teams” level we are looking to advanced roadmaps.

In future we would like to assign epics from projects to the different teams (using the advances roadmaps team feature).
When a issue gets assigned to a team how does the work end up on their board?
I assume it is based on board filters…
If so, what are (team) board filters best practices/requirements?
Do teams share the same big project or are (sub) projects per team and an overarching project the way to go?

Below is the current situation of how the teams operate:
TEAM A: Using a Scrum board with all issues from “Project Alpha”.

TEAM B: Using KanBan board with all issues from their active projects: currently “Project Bravo” and “Project Charlie”

TEAM C: Using 2 separate Scrum boards with respectively all issues from “Project Delta” and “Project Echo”.

Kind regards,




Log in or Sign up to comment