Sprints being renamed automatically

Ishita Mazumdar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 21, 2024

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.

 

2 answers

1 vote
Tobias H
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 21, 2024

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 

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 21, 2024

Hi @Ishita Mazumdar 

@Tobias H is correct.

Ishita Mazumdar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 21, 2024

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. 

Like Tobias H likes this
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 21, 2024

Hi @Ishita Mazumdar 

Re-naming an existing sprint is a manual action or an automation rule to achieve this.

Check the automation rules on the project.

Tomislav Tobijas _Koios_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 21, 2024

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:2024-10-21_12-31-55.png

Note that you need to be a Jira admin in order to access this page.

Like # people like this
Tobias H
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 21, 2024

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 

Like Ishita Mazumdar likes this
0 votes
Tomislav Tobijas _Koios_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 21, 2024

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events