Hi,
Sprint Name change in One agile board is reflecting in the Other board. Each agile board dedicates to a different project, there is no common thing in the board, still Sprint name change in one board is reflecting the name change in the Other board. how can we fix it.
is there any way to list the Sprint filed drop down (while creating an Issue) lists Sprints only from that Project?
Please help me out in this.
Hi Nagaraju,
A sprint is a separate entity that exists outside of projects, boards, etc. If you give a sprint the same name across different projects or agile boards, then this is the same sprint and making changes to it in one project will impact the sprint across projects. I would recommend that you rename your sprints so that they are unique and specific to your projects.
As far as getting the Sprint Field drop down to only list sprints within that project, I am not sure how to do this as I have never looked into it. To make it easier to fill out that field correctly, you could develop a consistent and simple naming convention for sprints. For example "<project key_team name_sprint number>" or something similar. We currently do "team name_sprint number" for ease of use and consistency.
I hope this was helpful.
Schuyler
I would agree, these are the same sprint. I would recommend checking out this KB: Sprints shared between multiple boards
I suspect that at least one issue that was in an active sprint A on board A, project A was then moved into project B, and board B. Doing this will cause that sprint that previously only appeared on board A to then also appear on board B.
If you are trying to restrict the issues in that sprint to only be issues in project A, then you would need to clear the sprint field for any issues (ie remove that issue from that sprint) before that issue is moved into a new project to prevent that sprint from appearing in board B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your response..
But is there any way to list the Sprint filed drop down (while creating an Issue) lists Sprints only from that Project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually no. Since sprints are project independent, it is possible that issues from any project could be added to any sprint. Jira does not have the means to restrict the possible values for the sprint field in an issue. There is an existing feature request to limit issues to only be able to added to specific sprints in https://jira.atlassian.com/browse/JSWSERVER-10805
There has not been any commitment yet to implement such a feature in Jira, but I would recommend watching that feature request for updates.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there any way to actually bring back to board to normal?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am having the same issues, i have one sprint that is showing up in two boards. How to get rid of that in one board?
Did anyone found solution for this issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Am also having the same issue if one finds a solution to this please note it down.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline 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.