Impact of renaming a status and its transitions in Jira Cloud

Asier Vadillo

We are using Jira Cloud with administrator permissions, and we are planning to rename a status and also rename the transitions that lead to this status.

The concern is that within Jira we have multiple dependencies: filters, automations, integrations with external tools (such as GitLab webhooks), etc.

We are aware that some filters will likely break — but which filters exactly will be affected?
What happens to issues that are currently in this status?
What should we take into account before modifying the name of a status and its transitions?
If possible, we would also appreciate any ideas or best practices to minimize the impact or fix the problems after making these changes.

Thanks in advance for your help!

Yogesh Mude_f9cg0f

@Asier Vadillo 

As you are already aware of remaining the status will imapct mostly on the Filters, automations etc.

Filters that are used in the dashobards, boards, reports etc and when you are trying to rename it. you can check how many workflows that status have been used and you can filter out those projects issues with specific status and once you get the project names then you will get the project specific filters as well ( not all but at least you will get an idea which project filters may impact)

The renaming status will automatically change for the existing issues and renaming transition name will not impact in anything.

Also, if the numer of renaming statuses are less then you can create a new status and then move all the issues of existing issues to the new one and then delete the existing one.