Sprints that are already named and prepared in the backlog already seem to get renamed to the name of another sprint in the backlog automatically.nNo new sprint is created, yet at random intervals the pre-existing ones are renamed. I'm not sure how or why this is triggered. If it is triggered by some action, I have been unable to figure it out yet. Any help would be appreciated.
Hi @Ishita Mazumdar and welcome to the community!
Yes, you are correct that when you create a new sprint it is automatically copying the name of the "lowest rank" sprint in your backlog.
It also does automatically upcounting, in case you have a sprint called "XYZ Sprint 1" the next will be called "XYZ Sprint 2" or if you use weeks like "Week 45" the next will be "Week 46".
This is out of the box, and to my knowledge it's not possible to turn if off.
Hope this helps!
Best, Tobias
@Tobias H is correct.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tobias H
Thank you for your response. My problem however is with sprints that are already prepared. No new sprint is created, yet at random intervals the pre-existing ones are renamed. I'm not sure how or why this is triggered.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Re-naming an existing sprint is a manual action or an automation rule to achieve this.
Check the automation rules on the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for jumping in here - just a quick info.
Information about updated sprint names should be visible in the Jira audit log - https://<SITE-NAME>.atlassian.net/auditing/view. So you could also check out there to see how sprint was renamed:
Note that you need to be a Jira admin in order to access this page.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, as both Marc and Tomislav have pointed out, this must either be a manual change from a colleague or an automation that triggers based on some value change (in case this occurs "randomly").
And you would be able to find it in the logs that the sprint has been renamed, which should make it easier to investigate :D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ishita,
Currently, there's no way to (re)configure this (even though some people already asked for functionality to be able to configure the naming pattern).
Here are some JAC suggestions you can take a look at and vote for, although similar requests were declined in the past as the majority of users were okay with auto-generated names and number increments.
Cheers,
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.