I have two projects that have an active sprint with the same identifier number. Now when i change the label for one sprint in one project, it changes the label for a sprint in another project. How can I change the name of one of the sprints and not have it affect another sprint?
Hi Zan,
Here is the issue I filed, but it was set to resolved as it is known behavior:
https://jira.atlassian.com/browse/GHS-11250
I think I will have to re-submit it as an improvement request.
-John
Hi @john kaplan] and [~elisa diel [atlassian] I agree with John, this shouldn't be marked as resolved. I've posted a comment on the issue referenced as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This causes big problems for us... Most groups only have access to their project, and they create names like "Sprint 1" and so they step all over each other and then complain when they don't have access to close the sprint. It creates a huge support/administrative mess.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi - is there a resolution for this yet? I am having same issue.
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same problem - I have two projects but since running sprints in each the numbering has gone out of sync when I try searching in filters.
@John Kaplan do you have the issue number you raised?
Tx,
Zan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Elisa,
I raised an issue, trying to work through it now.
Thank You!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure thing! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
We might have to change it directly on the database. Could you please raise a ticket on Atlassian SAC (support.atlassian.com) under JIRA Cloud so we can better investigate it?
Cheers!
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.