When I have multiple Jira projects sharing same sprint name, how can I know which sprint should be chosen in Jira ticket for current projects?
There is no indication which sprint belongs to which projects.
Hi @[deleted] ,
The sprint is globally visible, so I think the easiest way is to define the sprint naming rules by the team to distinguish them, such as the project name + iteration start date.
It is indeed a good practice, but does not answer the question.
Let say even if you had a convention like this in place, but someone does not follow it, you want to find which project it comes form and help them follow the best practice.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sprints don't belong to projects, so the question is not actually answerable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can always rename the sprints thereby not having this problem. Scrum Master or whoever has 'Manage Sprints' permissions and is creating the sprints, can change the sprint name, dates, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Plus, sprints don't "belong" to projects. They include issues from one or many projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But if I choose a wrong sprint ID(same sprint name), it will be lost from my own project backlog, because the sprint value is wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So before choosing the sprint, make sure to rename the Sprints so that there are no conflicting names. Inform your Scrum Master or whoever has access to 'Manage Sprints' to rename the sprints.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a workaround to delete these orphaned future sprints..:
Add one of the orphaned sprints to an Issue from any project. Go to the Backlog view, and then you can delete the sprint from there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.