For the problem described in KB (Sprints shared between multiple boards), I need to find a solution for this problem or evaluate some alternatives to JIRA and/or JIRA Agile. If you have the same problem like us and find some solution for that, please share it with me.
Here are symptoms:
and this is my comment there:
Another problem exist here and I describe it:
1- Consider you have two boards(each for 1 component or subsystem) for 1 project and each board belongs to specific persons without any persons exist in both of them.
2- Consider a bug has been raised and you assign it to a person in an sprint in board 1 wrongly.
3- Now You want to reassign it to another person who belong to another board. If you do this, an sprint auto created in board 2 with the same sprint name at board 1 and you have to do some more stage to avoid this problem
I hope to Atlassian see this as a bug not a feature.
Thanks in advance
I think the sprint is showing up in different boards because there are issues in that sprint that belong to both boards.
You should look carefully to the filter query of the board configuration. Every issue should belong to one board, your filter query should ensure that.
A sprint that belongs to more than one board can be closed in any board. If it is closed in one board, it will be closed in the other boards too.
Hope that helps
I have a similar problem, and I dont know how did it manifest in the first place. I have a sprint I created in a project, which has its own board. Now the sprint shows up in different projects and boards. It has the same unique ID associated with the sprint. If I make change to the sprint name, in one board, it reflects in other boards too. I need to have unique sprint names, in all projects. Can somebody please explain why is this happening?
Is there a resolution to this? I am new to this company and it appears that all projects are under the same sprint. If I change, for example, the end date of the sprint...all projects sprint end dates change. I would like to allow one or more projects to be on a different sprint cadence. Any ideas?
@Jason Cagle sprints belong to boards. from what you described, there must be a jira board somewhere that is pulling issues from your project into their sprint.
here is some guidance:
its possible that your company wants everyone on the same sprint cadence and is doing this purposefully (although, there are other ways to achieve this)
@Mike Solomon I may be misunderstanding your response, but I don't think it's the issue I am having. I'm having an issue that, if I go into my backlog and Edit the current sprint and change the end date, this changes the end date of all projects because, it appears, that all projects are under that same sprint. So, it seems to me that I need to basically create a new sprint and move my project under that new sprint...and that's the only project under that.
Or, maybe I'm misunderstanding your response above??
if I go into my backlog and Edit the current sprint and change the end date, this changes the end date of all projects
Right, let me clarify... sprints originate from a single board (the board they are created on) but can appear in more than one place.
Let's say there's Board A... it pulls issues from multiple projects. Someone creates a sprint on Board A with a bunch of issues from multiple projects in the sprint.
Then there's Board B... your board. It only pulls issues from your project. Board B will include the sprint that was created on Board A because some of the issues in that sprint show up on both boards. If you modify the sprint's attributes on Board B, it will be reflected on Board A (and where ever else the sprint appears).
A way around this is to make sure that Board A isn't including your issues in the sprints that they create.
Let me know if that helps
I am facing the same problem , 2 Different project - with unique issues have a common sprint. Any changes made via Project 1 impacts the sprint for Project 2 and visa versa.
Upon initial analysis -
1. There are no common issues/Epics between the projects.
2. I have 10 diff projects but the issue observed only between 2 projects.
3. I have tried mutiple combinations but am unbale to decouple the 2 projects.
If you move an issue from Project A to Project B, the issue will retain it's old Sprint value.
Therefore, the board of Project B will now have an issue that belongs to a sprint in Project A.
Use your board's Velocity Chart to detect Sprints that don't seem to be reporting correctly. They usually contain issues that were moved. Bulk change those issues to remove the bad Sprint value and it should be good to go.
This used to be an issues for us all the time. We have multiple teams working on one project but each team having a unique board. As we start putting issues into sprints it becomes messy keeping track of it in multiple boards, having the wrong sprint sometimes show up in the wrong place. We finally solved it by using an addon to group multiple boatds into a single view, grouping each board issues into sprints that are shared accross all of them. So even thougth the sprints show up in all teh boards the issues are unique for each boards and since you are looking at all of them at the same time in one view it makes it easier to follow along as oposed to switcghing between multiple boards/vierws. https://marketplace.atlassian.com/plugins/early-bird-planner-prod/cloud/overview
I think it's pretty bogus of Atlassian to not allow sprints to be applied across multiple boards within a distinct project. That means if I have 2 teams within a project, I have to create 2 completedl separate sprints for each team (board). And then to force people to buy an additional add on, in addition to what we're already paying atlassian for licenses, is really bogus.
@Keith Horlock I've seen this set this up in my cloud instance...
1 Board for Team A
1 Board for Team B
1 Board containing both teams
The board that contains both teams is is where the Sprint is created and planned. The board for Team A will only show issues that are assigned to Team A in the current Sprint. The board for Team B will only show issues that are assigned to Team B in the current Sprint. No add-on necessary.
Personally, this isn't how my team is setup but I've seen it done.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
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!
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