Best Practices in JIRA

[Nagendra Dattatreya]

Currently we have 5 different scrum teams working on the same project. What is the best way to setup JIRA so we only see backlog, issues, releases for their own team? I have created 5 different boards with specific filters. But when you click on releases or All issues, it shows data for all teams. Is it better to setup 5 different projects or is there a way to limit the visibility for each team? 

The reports also does not show the burndown or velocity chart by each scrum team.

[Alexey Matveev · Accepted solution]

Hello,

How do you identify that an issue belongs to a team? You should add this condition to each filter defined for the created boards. You can find filter if you go to board settings -> general.

[Nagendra Dattatreya]

Thanks Alexey! I created 6 diff boards, one for each team. 

[Warren · Accepted solution]

Hi Nagendra

I would definitely say that you shouldn't create 5 projects, that would be a nightmare. As Alexey said, you need a differentiator for each team - this is usually set up as a component or label, so team 1 could have component = Team1 etc. This is then added to the specific filter for each team's board.

You would then also create a separate sprint for each team, even if all the sprints run concurrently (which they probably should).

Hope this helps

[Nagendra Dattatreya]

Thanks! I created 6 diff boards, one for each team. I can now control the backlog based on the board. I am storing the team name in labels which is included as a filter for the board

[ialexand]

If the 5 teams are working on the project at the same time and using the same issue types and workflow then you have to differentiate each sub team somehow.

If different teams work on an item at different stages, this becomes easier:

For example: for a support team

You could have a board for investigation where the final status is either "done" or -> "to Development"

This status then appears in the backlog column of the Dev Team

when they are finished their final statuses are "done" or "To Test"  when that item will then appear on the testing team's backlog.

That's a good way to allow just different teams to only see items that they care about and items that they need to work on. The downside for the manager or product owner is that they then have to track an issue across multiple boards. If that is a problem you could create an Overview board that shows just which team an item is with.

If they're all working on items in the same state at the same time, then you have to either use labels or components or clients or else create your own custom field that applies to each team.

For Example: 

You could have  custom check boxes for "Team 1" "Team 2" "Team 3" etc and when it's checked it appears on their board.