I have a user that is a project admin on two different projects. A cleanup oif sprints on one project was needed, so he did this. the result is that his two project sprint boards are now mirrored from a Sprint naming Point of view. He cannot change one project's sprint names without affecting the other.
Is there somehow a linking between these two very distinct, very different projects that was made , and that could be removed?
This is the sprints expected behaviour. Despite you can only create a sprint when you’re accessing a board, the sprint is not exclusively tied to this board and project, sprints are global.
It is possible to add issues from any scrum project to the sprints, the board is just a way of creating filters to show issues and metrics grouped by project.
In other words, if you access 'Project 1' board, create a sprint named 'Sprint 1', then access 'Project 2', create 'Sprint 2', you will have two different sprints that can be accessed from plan mode independent of the board you are accessing, either 'Project 1' or 'Project 2'.
We are trying to keep sprints named after project as well. But every now and then they get mixed up. The other day I woke up to see project A's sprints gone and instead project B's sprints on the board with tasks from project A assigned to them. Nobody knows how on earth that happen, and now we need to clean up that mess. I guess this is expected behaviour...
This issue is inconsistent and needs to be fixed, please.
I'm the scrum master on 4 different projects. One just recently started linking it's Sprint names to another project and the cycle isn't breakable. I've tried moving all the stories into a newly created sprint and then deleting the duplicated named sprint and then the other scrum board updates by deleting the sprint name but keeping the content of the deleted sprint under the name of the next sprint name of the other board.
This issue has been posted since 2014... is there really nothing being done to find a better solution?
Thanks for your time and consideration.
@Branden McElveen SAME issue!
why do we have to use a workaround ... does not make life any easier... have been using this for over 6 months with more than 10 sprints on each project following their own naming convention but only NOW the names of sprints starts to get mixed up between projects!!! what is up with that! .. thanks
In our case we need to run multiple sprints at the same time which belong to different projects and thus my solutuon so far is:
1) Create sprints with different names. I use [Project Key(example: TW] and [Sprint number (example: Sprint 2].
2) Then select run sprints in parallel using instructions found on ths wiki:
"This is the sprints expected behaviour. Despite you can only create a sprint when you’re accessing a board, the sprint is not exclusively tied to this board and project, sprints are global."
So, creating and starting a new sprint in Project 1, also starts the BACKLOG of Project 2. No, this is not expected behavior. This is very much a problem.
So, I am running 5 development teams in 5 seperate projects and have standardised SOP across the board.
Result: all sprints have the same designation in each seperate project.
Unintended consequence of the above: sprint names randomly change as we do planning
I now have to break standardisation so each project sprint becomes unique?!?
Bad design if you ask me. At least warn me if you are going to merge sprints across projects? Common courtesy...
This is so annoying. I just created a sprint in our iOS project, that for some reason also created a new sprint in our Android project. I now can't start my real Android sprint since it says I have an ongoing sprint already...but in the Android project that sprint is empty. Since it only contains iOS tickets
I get that boards can be shared between projects, that's great. But projects shouldn't share stuff like this..
We have this problem also. I do not think it is created by the user being Admin on 2 projects. I was not Admin on the other project - problem is Sprints can be used by multiple projects.
JIRA automatically offers default names for each new sprint. The names are Sprint 1, Sprint 2, Sprint 3 etc. But these names are not exclusive to the project. As we discovered to our cost, when I suddenly couldn't start Sprint 3 because another project had a Sprint 3. You can't even rename your own sprint because it is shared by the other project. The original questioner would have been able to do this because they were admin on both projects.
We fixed this by creating an entirely new empty sprint (system was calling it sprint 5 but we changed it) with a name "Project Sprint 3". Then we copied all our issues from our existing Sprint 3 to the new "Project Sprint 3". Then I was able to start the "Project Sprint 3".
We now have guidelines that you must use your project name in your sprint names. I think this is poor functionality on JIRA's part - you should be able to set it up so projects do not share sprints, as this would be common usage. Having to manually change the sprint names is counter intuitive.
I hope our fix helps someone. I would like JIRA to change this.
Does anybody know if this was resolved, and how. I am having the same issue. Changed a sprint name on One Board, and it reflects in some other board. This is creating too many reporting and tracking issues. I have multiple projects, and every project is on different sprint. But why all of a sudden is this happening.
I just ran into this bug. Had two projects, sprint names that could previously be named independently started to sync across projects. I think this may have been triggered by moving issues between the two projects?
I was able to stop it by creating two new sprints in both projects, moving tickets into those respective new sprints, and renaming them both.
Now I can't separate the sprints in each project. Even if I create a new sprint in each project with a unique name to that project. Whichever project creates the newest sprint will then become the sprint for the other project.
WTF is this feature and how to do we work around it????
I think this has been eluded to in some responses but not fully called out. Here is what we found when this happened to us as well. Sprints are global and not project specific. So in our example we had Project A that created "Example Sprint 1" and then Project B that created "Example Sprint 1". Both sprints named the exact same. Project A assigned their stories to the "Example Sprint 1" that they created, so all is good. Project B assigned their stories to the "Example Sprint 1" that Project A created. When you go into an issue/story and assign a Sprint there is no identifier saying what project a sprint was created in (because Sprints are global). It would be nice if Atlassian prevented Sprints from being named the same. So Project B thought they were assigning everything correctly. This has led us to put some suggested standards in place around Sprint naming to avoid this happening again. Like including the Project Key in front of the Sprint Name (ABC Sprint 1). It's a nice feature for cross project collaboration but also something that can be dangerous if project teams aren't aware of how it works. Hopefully this helps.
I don't fully understand the scenario where this would be desired behaviour.
We created different Jira projects in order to separate the concerns and development cadences of our teams, but yet they're not fully separated? This feels like something desirable only for organizations where absolutely everyone functions on the same sprint cadence, but in the vast majority of cases, it absolutely feels like something you "just need to work around".
...steemed Steve Elliot (head of product for Jira Align). Agenda: What’s new or changed in SAFe 5.0: Introduction of OKRs Essential SAFe How to achieve true business a...
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