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.
When working with multiple boards on the same project, there are several ways to differentiate between them.
People who encountered with this challenge and found a solution that works - I will be happy to learn from your experience
I'm guessing you mean "differenciate at a glance" because as Kat said the name is a really obvious difference.
If you're working with a relatively small group of boards a quick fix could be just editing the color of the gadgets in each of those boards.
Hope it helps.
@lago, @Kathalin Alsmeier - Thank you for your answers
I should have been more clear on my request -
We are working on one project, with one backlog of our product, and multiple scrum teams
For that, we have issued several boards (on the same project)
The target is that each of the boards will only see 'it's own' Epics/Stories/Bugs/etc..
I read that that labels is one option, however - I am looking for a better ways for differentiate...
Ok, then. I believe I understand better this time.
You don't have to configure each board itself. You have to configure each gadget in each of the boards you have to show those issues.
Instead of configuring your gadgets to show results from a particular project you must define a series of JQL filters that suit your needs and configure your gadgets to show the results for the filter you want.
On top of that, you could assign a color to each team as a visual hint so they instanctly know they're looking at the information they're suposed to.
I hope that is what you're looking for.
G'day @Yogev Tal ,
On the Jira Align team we spend a lot of time helping customers delineate their scrum teams across boards and projects as they scale agile to the enterprise in Jira Align.
Our recommended practice for Jira Align would be sticking each scrum team on its own Jira Project and having a completely separate Project for the Program (Epic) backlog that all teams work towards. You can bring in Jira Epics on your team scrum boards (projects) using filter queries such as Project = A or (Project = B and issuetype = epic)
When using multiple scrum boards under a single Project we recommend naming the boards after the scrum teams and creating a custom team field (single select list) that contains all the team names. You can assign the issues their team using the custom field and utilize a filter query such as Project = A and Team = Apple
I hope this helps provide some ideas!
Hey @Tim Keyes ,
Thanks for the reply
We have eventually used the Component field to distinguish between the scrum boards
Since this field is supported from Epic level through sub-task, it allowed us to have a full separation between the teams backlog while working on the same project