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
I have created multiple scrum boards within the same projects but the problem is that they all have the same statuses.
I want to create boards because I don't want to manage the different module in the same boards.
Here what it is:
I have one project with multiple modules and these different modules are assigned to different teams. I want to create multiple boards so that each team can work on their module.
For e.g If a ticket is created in Module 1 board then it shouldn't show this ticket in Module 2 boards and same goes for other modules with their boards.
I hope I have made my question clear.
I'll be grateful if someone can provide me an urgent solution for this.
I think you might have misunderstood what boards do. They are not containers of issues, they are a view of a selection of the issues. An issue might be seen in many boards, but all of the boards show the issue as it is, they don't contain it.
You need to come up with a way to identify which issues belong to which team, then modify each team board such that it only selects issues for that team.
The most obvious option is to create a "team" custom field, and then modify each team board's filter so that it includes "and team = X", but I usually find team selection for a filter is a bit more complex than just a single field (a common one is "and team = X or label = team-x")
It is much the same answer - boards are a view, not a container. If you want different views, you'll need to configure your boards to show those different views.
A custom field is a very good way to do that.
Because system fields try to be a bit more "clever", you may have to think more about how to do it with them, which is why I lean towards doing this with custom fields (or components and labels, they're the two system fields that work best for this)
It can be done, but you have to use components, labels, or a custom field to do it. Then you will have to change the filter on each board so that they only pick up the issues that relates to that board.
I would recommend using components since you can then control those from project settings.