Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issues with starting Sprint in multiple Scrum Boards under 1 project

Arushi Verma January 12, 2023

Scenario: I'm having multiple Scrum boards under 1 project and maintaining different stories backlog. 
Issue: 

Starting Sprint 15 of Scrum Board 1 is fine. 
But when starting Sprint15 of Scrum Board 2, pop-message says it's connected to the User stories of Scrum Board 1 Sprint 16 with a hidden query and pulling those into the current sprint (Sprint 15), messing the Scrum Board 1's Sprint 15 scope and renaming the Sprint 16 to 15 in this 1st Board.
Note: This issue was not happening on the non-cloud version of JIRA previously. 

I have checked the filter queries for both the Scrum boards and they're different.

1 answer

1 vote
Ste Wright
Community Champion
January 12, 2023

Hi @Arushi Verma 

Can I just confirm the steps to reproduce this:

  1. You have two Scrum Boards in one Project
  2. The Boards have unique Filters - i.e Issues are not shared between the two Boards
  3. You are starting two separate Sprints to run at the same time

And one think to check:

  • There are no Issues which are in the wrong Sprint/both Sprints - i.e no-one has added the data manually using the field, rather than drag/drop on the Board - usually this happens if Sprint names are similar/the same

^ I replicated the steps I currently have listed above - and it worked fine for me, with no error.

Perhaps a screenshot of the error would also be useful here :)

Ste

Arushi Verma January 12, 2023

Hi @Ste Wright 

The Sprint names were same, so maybe someone might have added the data manually in the Sprint.

I will try to test this out again after 2 weeks (since my current sprint has already started and I don't want to take any risks)

Thank you so much for your quick reply. I'll post back if I face any issues regarding this in next sprint.

Like Ste Wright likes this
Ste Wright
Community Champion
January 12, 2023

No worries!

I would recommend testing it in a separate Project if possible (i.e a test/dummy Project).

That way you can trial different scenarios without impacting actual live data, or waiting 2 weeks each time to try different things!

Ste

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events