Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

1 Jira Project, 2 Boards (by separate Component), 2 Sprints. One Sprint name updates other

We have Jira v8.5.8. One Jira project A. Two scrum boards of same project (Board B1, Board B2) with respective filters for Component C1 and Component C2. Update of Sprint D1 (name) of Board B1 automatically updates the Sprint D2 (name) of Board B2. 

Any idea, why this happens.?

1 answer

Hello @Suresh Mantrala 

Welcome to the community.

A sprint will be visible in a board if either of the following conditions are met:

1. the sprint was created in that board

2. the sprint contains issues that are within the scope of the board's filter.

So, it would appear that you actually have one sprint showing up in two boards, probably because at some point an issue in each board got added to the sprint.

Note that there is nothing in JIRA that prevents you from creating multiple sprints with the same name. So, if your teams are using simple sprint names like Sprint 1, Sprint 2, and Sprint 3, then JIRA would allow you to do that. That can lead to confusion if somebody edits the Sprint field for an issue and selects the "wrong" sprint named Sprint 1. I always made a point of training my users to create sprint names that would be obviously unique to their team/board

When a sprint is showing up in two boards, any change made to the sprint in one board will show up in the other board, as it is really one sprint entity.

To resolve this I recommend that you have each team create a brand new sprint in their own board and move all their issues from the erroneously "shared" sprint to their newly created sprint.

I just provided names to make a case. Actually both names of Boards and Sprints are different (I checked the Sprint IDs and they are different and hence cannot be a "SHARED" sprint), filters of are different (separate components). 

Please provide more details on exactly what you are updating in Sprint D1 and how that is impacting Sprint D2.

Sprint D1's name - Finance 20.1.1 and Sprint D2's name - HR 20.1.1

If I update Sprint D1's name to Payroll 20.1.1, Sprint D2's name is getting updated as Payroll 20.1.1.

In that case, the sprint being used in the second board is, in fact, the same sprint being used in the first board. The sprint is being Shared.

How did you validate that the "two" sprints (one appearing in each board) have different IDs? It would help is you provide screen images that show what you see in the boards and what you see when figuring out the sprint IDs.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Bitbucket Smart Commits vs. Genius Commits - What's the difference?

If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...

106 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you