Changing the status name

[Paulina Mijal]

Dear all, 

In the flow that is used, I want to change the status name from "x" to "y". What changes and possible complications will this cause? If the status is used in filters will it change automatically?

Thanks,

[Peter-Dave Sheehan]

If you change the Status name from inside the workflow editor it will change that status EVERYWHERE including any other workflows that use this status. Existing filters and dashboards that point to x will break until you manually rewrite them to point to y.

Do this VERY carefully.

In most cases in a large instance with many projects and workflow, it is better to create a new status with the new name and adjust all the transition arrows to point to the new status, then delete the old status.

[Radek Dostál]

It will only remap the status in your existing workflows and issues, but it will not do anything with JQL or any automation you might have with the status name hardcoded.

JQL is stored as plain text, there is no reference to status in terms of statusid, so you need to update those manually.

Automation - this depends on the app and implementation. Generally if it's plain texted, then that falls to the manual category. If it's from a selector then more likely than not, it will be linked to statusId in the background so that should be fine. Again though, this depends on the vendor/implementation so no guarantees.

As for dashboard reports and board column mapping - my understanding is that those are linked by statusId, so they should be fine - it's just the jql.

In case of any doubts, you might want to confirm this on a test instance or with some test issue subset - none of these are exactly documented what will or will not map as far as I know, so it's more of a practice and general understanding of how things are connected to one another.