Multiple Scrum Boards report the same Sprint

Nabil Sayegh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 4, 2013

When viewing reports for diverse boards, we noticed, that some sprints are in multiple boards.

The sprints have the same JIRA-internal id. But only one report shows the real issues and chart. Is that a bug?

See the attached screenshots for boards 35 and 45, both with sprint 42:

2 answers

1 accepted

0 votes
Answer accepted
EddieW
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 5, 2013

If the sprints have the same ID (visible in URL) then that sounds like an issue in the board config. Try removing the empty board an re-creating with a filter distinct from the first to prevent overlap.

Otherwise GH is designed to let multiple sprinnts show on the same board, or the same sprint on multiple boards - that is expected.

Nabil Sayegh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 5, 2013

The other board isn't empty, it's a valid board with it's own sprints and disjunct projects, so I can't delete it.

I just wonder why the same sprints (with same id) appear in reports of different boards.

EddieW
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 7, 2013

The sprints shown on a board are bases on the issues shown on the board.

There must be 1 or more issues visible on both boards. Refine your filters to eliminate that.

Like Eva Fernandez likes this
Elber Carneiro October 23, 2018

Can verify that even after changing the issue to associate with a different sprint, Jira still 'remembers' the association and in fact there is NOT an issue on both boards currently.

Like Spencer Viray likes this
0 votes
Danilo Conrad
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 23, 2015

For those who may come across this post in the future, this problem is described in more detail in the article below:

 

Suggest an answer

Log in or Sign up to answer