Summary

In the Jira old workflow editor, when a status is initially added to a workflow, the global transition leading into that status is named the same as the status itself.

However, if the status is renamed later, the transition name does not change. This unchanged transition name appears in various locations, such as the transition dropdown on the main issue view, the transition screen header, and in bulk operations under the "Available Workflow Actions" column.

This situation can confuse end users as processes evolve with workflows, requiring terminology alignment. Additionally, it increases administrative overhead due to discrepancies in naming conventions, necessitating manual cleanup tasks.

Steps to Reproduce:

Example steps to reproduce behavior:

• Open workflow in the old workflow editor
• Add a status named "test" to a workflow
• select "all statuses can transition to this issue"
• Rename the status to "Renamed Status"
• Publish the workflow
• Do a Bulk transition operation or select the transition dropdown of an issue associated to the workflow
• Observe that there is an option for "test" > "Renamed Status" is present causing confusion

Workarounds:

1. Use the new workflow editor for workflow updates - this will update the name of connected global transitions when a status name is updated (currently does not support setting customised global transition names). The new workflow editor can be accessed under the "switch editor" menu in the old workflow editor.
2. Edit the name of the global transition in the old workflow editor to align it to the updated status name.

Suggestions:

1. Update messaging in the edit status modal to inform users that connected global transitions will not be renamed.
2. Ask customers when renaming a status whether a connected global transitions should be updated to reflect the updated status name (allowing customers to preserve customised global transition names). This will have done two valuable things:
   1. Immediately informed the admin making the status change that there is a difference between the two and that difference matters for aligning workflow terminology
   2. Will allow an Admin to change the setting with a single step in that resulting modal pop-up which Saves on manual cleanup intervention and administrative overhead once the discrepancy is discovered