Sprint name has changed

[Samantha Moy]

HI Everyone,

I have a custom filter that is shared with the team that we use for each sprint.   Team managed project.  I am the admin

My sprint filters are no longer coming back with results bc the sprint name has changed.   No one on our team has changed them.

We are currently are on sprint=137    At some point after 8:30am  PST time today the sprint name changed to Sprint-cf[10122]

How do I fix this?

Thank you, Sam

[Samantha Moy · Accepted solution]

An employee created a new project and was not aware of the downstream project impast of his changes.   Changes have been reverted back and we filters are working as intended.  

[Kseniia Trushnikova]

Hi @Samantha Moy,

Now your filter is cf[10122] = 137, but before it was sprint=137? If so, it looks like another custom field called Sprint has been created in the system. Please contact your Jira system administrator to check this (System > Issues > Custom fields).

If there're several fields with the same name, Jira refers to their IDs. cf[10122] is the ID of some custom field.

Correct me if I misunderstand your issue.

[Samantha Moy]

Thank you Kseniia,  You understood correctly.  I am the only admin.   I was wondering if the updates made yesterday ~10am PSt affected my filter?? 

When I tried to access the documentation I received a 404 error.  Is it not completed yet?   JIRA work Mgmt/Save your filters

https://confluence.atlassian.com/cloud/blog/2023/07/atlassian-cloud-changes-jul-17-to-jul-24-2023#AtlassianCloudchangesJul17toJul24,2023-jira.work.management

Thank you for your help.

Sam

[Kseniia Trushnikova]

@Samantha Moy, are you using Jira Cloud? That's the changes rolling out to Atlassian Cloud sites.

I don't think that these changes can affect your filter... As a first step, please make sure you have only one field named Sprint. Go to System > Issues > Custom fields for this.

[Samantha Moy]

Hi @ksel

    Our sprint filters have started working again.   Do you know what has changed on the Atlassian side.  None of us changed or added custom fields.    Thank you.

[Kseniia Trushnikova]

@Samantha Moy, that's interesting. Then it really looks like the Jira Cloud updates might have affected the filter.

Sorry, I don't know what has changed on the Atlassian side. I am just a Jira administrator like you :)