I know this issue is partially existing in other questions relating to tickets in other sprints displaying on boards but my concern is specific to the creation of a ticket.
When you create a ticket in project A, the sprint drop down field displays all available sprints from Project A, Project B, Project C etc.
Creating a ticket for a project should only be able to be added to a sprint in that project.
UPDATE - Vote for this functionality here: https://jira.atlassian.com/browse/JSWSERVER-10805
Currently, there does not seem to be anything that limits which Sprint an issue can be added into when done via the Issue View Screen (with the 'Sprint' field). This can cause confusion as it could show Sprints from boards from a different project or cause users to link the issue to the wrong Sprint due to Sprints having the same name.
The suggested workaround is as follows:
Since Sprint names are not unique in JIRA, try using unique Sprint names with a prefix of the Project so that it will be easier to distinguish them.
At this time I would recommend going to JSWSERVER-10805, voting on the issue and leaving comments for the developers so that feature request can gain additional impact so it can be added to JIRA.
Thanks. Have updated the original question to direct others to the issue. I can see the issue was created in 2014 and hasn't been done yet.
Since 2014, Aaron Mooy has:
That's a lot of progress so I am a little concerned at the comparitive lack of progress of this issue.
I currently am facing this issue. I closed a sprint because a projectadmin wasnt able to. 2 iriitated customer calls later i really wish there would be a possibility to limit sprints to projects, since it turned out i closed the sprint of another project. Nothing major, and could probably have been avoided had i looked closer, but still. Come on JIRA.
Please fix this! It's terrible UX.
Every week someone accidentally assigns a task to a sprint in another project - which in turn causes all sorts of issues when trying to create new sprints, other automation rules, etc. We only have 15 users in Jira, how a large organisation with 100s of users can bear this I can't imagine!
The linked issue at the top of the page has been marked as resolved, but this appears to be for the on-prem version. The Cloud version https://jira.atlassian.com/browse/JSWCLOUD-10805 is still open which is ridiculous! This is a really frustrating problem that needs a resolution!
Great, just came to the board to figure out how to do this and it looks like I can't and it's been an outstanding issue for a long time. We inherited a classic project from our third-party vendor when we started our in-house dev team. Simplifying our going-forward work with a Next-Gen project and love it so far except the Sprint list that includes dozens of outstanding Sprints that were apparently from the previous vendor's other client projects. Those projects aren't even in our version but I still see them.
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