Problem with 2 boards that get the same sprint

I have created one project and a configured field named "Team" to separate between boards of different teams that work on the same project.

There are ~10 teams that work on that project, only epics and versions are mutual.

For 2 teams, the sprint somehow became mutual too. if I change the name in one board it is reflected also on the other. Yet, the issues that are linked to the sprint are different and shows correctly per team field.

I do have another board to reflect the entire project for all teams.

Any idea why this happened and what can I do to fix?

All other teams that works on the same project seems fine.

We have Jira 6.1.3



2 answers

1 accepted

1 vote
Answer accepted

Hi Michal,

It seems that those teams are both using the same sprint, this probably happened because in your main board (with all teams ) you've created that sprint and added tasks for both teams to that sprint instead of only tasks for one team.

You could create another sprint and move all the tasks from one team into this newly created sprint.

Best regards,



Thanks for the quick response.

Currently I could not find any issues that are mutual to both teams.

If I will create new sprint to one of the teams and move the issues to that sprint, how will I delete the old sprint from that board? wouldn't it be deleted for the other team as well?


Hi Michal,

If no more issues assigned to that team are in the Sprint it should automatically disappear from the board.

JIRA Agile boards only show sprints that contain issues that are part of the boards filter, so if the sprint no longer contains any issues from this filter it will no longer be shown on the board.

Best regards,


Check the epics... are there epics common to those two boards in particular?

Epics are also not part of a dedicated sprint in JIRA Agile. So you can have Epics across boards without having Sprints across boards.

Epics are common but this was the idea of one project - we have several teams that are working on same epics (different stories for each team).

We have this configuration for several teams but the problem occur only for 2 teams.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

656 views 0 7
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you