How to set up JIRA for 2 teams on the same backlog so that the JIRA-Reports work correctly?

[Joachim Schittenhelm]

How do we have to setup JIRA that all the reports work properly when working with multiple teams on one backlog?

Our current setup:

• parallel sprints enabled
• 2 "Backlog-Sprints" labeled "Backlog Team A" and "Backlog Team B"
• 2 active Sprint like "Team A - Sprint 100" and "Team B - Sprint 100"

where Team A works on Epic A and Release A and Team B works on Epic B and Release B.

The problem is, that reports like the Release Burndown do not work properly as the Sprints on Team B (that work on Epic/Release B) are shown when looking at the Release Burndown of Release A.

Our first idea is to create Boards that just contain the Sprints of Team A (or Team B). But it's not possible to filter the name of the sprint with "~". Therefore we would have to alter the filter of the board with every new sprint (Team A - Sprint 101, Team A - Sprint 102,...).

Is there a better possibility to solve our problem?

[Vinh Bao]

Looks like I have the same issue shown incorrectly in Epic Burndown when multiple teams working on

Steps to Reproduce

Create a project call TEST
Create a custom field (text field) call Team.
Create two filters:
Team A: JQL: project = TEST and Team = Seal
Team B: JQL: project = TEST and Team = Sparta
Assign Team Seal value to TEST-1
Assign Team Sparta value to TEST-2
Create two issues TEST-1 and TEST-2
Create two board Team Seal and Team Sparta and use the Team Seal and Sparta filters
Create a board by including Team Seal and Team Sparta with the JQL query (project = TEST)
Create an Epic call Team Redshift and link TEST-1 and TEST-2 together.
Add a sprint for Team Seal and Sparta board with different name. and same duration, Start Date, End Date
Set a story point to TEST-1 and TEST-2
Transit TEST-1 and TEST-2 to Done.
Ended the two Sprint and view the Epic Burndown chart

Expected Results

• Seal Sprint 2 and Sparta Sprint 2 should merge together as the same duration, Start Date, End Date

• Seal Sprint 3 and Sparta Sprint 3 should merge together as they have the same duration, Start Date, End Date

•  Velocity forecast should based on average velocity of last 3 sprints by time and having story points eat up.

Actual Results

• Seal Sprint 2 and Sparta Sprint 2 don't merge together although they they have the same duration, Start Date, End Date

• Seal Sprint 3 and Sparta Sprint 3 don't merge together although they have the same duration, Start Date, End Date

•  Velocity forecast isn't correct, it based on average velocity of last 3 sprints by order

   

[willw-bhp]

Was hoping someone might have found solutions or to learn Atlassian have made an enhancement to fix. This has been a long standing issues and I suspect it force some people to split JIRA projects, which in itself cause much worse problems when trying to run a mature Scaled Scrum set up with a single PO and limited local optimisation.

JIRA portfolio has the notion of teams but JIRA itself does not. Adding this feature might be one way to solve it.

I have raised it as a suggested enhancement

https://jira.atlassian.com/browse/JRACLOUD-71828

[Joachim Schittenhelm]

as far as I see, this is a bug...

[Joachim Schittenhelm]

@Peter DeWitt This does not work properly either.

We already got a different release for each team as they are working on different features. (completely different, nothing in common)

But when I open this report ALL the sprints of both teams are listed and somehow count towards the release. It seems quite stupid, but I do not get my mistake (or JIRA's mistake).

[Peter DeWitt]

Hmmm. Let me test it out here and I'll let you know.

[Joachim Schittenhelm]

@Peter DeWitt thanks a lot

as far as I see JIRA mixes up the assignment of issues to sprints!

Team Orange (with all their MP <number> Orange - Sprints) does not at all work on this release!

[Peter DeWitt]

@Joachim Schittenhelm, Sorry for the mis-understanding.  That report is not going to key off of the sprints (they wont matter).  What you will need to do is create a separate release for each team (sprint).  For example, Release #1 - Team A & Realease #1 - Team B.  This will let you essentially view each sprints work on this report.  Not a perfect solution but the best Jira can do.

pjd

[Joachim Schittenhelm]

@Peter DeWitt I meant a different report. The regular burndown chart works perfectly fine.

But the Release Burndown does not (with our setup). 

I meant this report:

[Peter DeWitt]

@Joachim Schittenhelm, you should be able to specify what sprint you are looking at in the burndown report.  We have 3 teams using a single project with 3 different sprints. The dropdown below should show you your current sprints as well as any past sprints.

pjd