Summary

In Jira, when a status is initially added to a workflow, the 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:

• 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

NOTES and Suggestion:

The intention of this functionality is that the transition names can be customized, and renaming a status should not impact the workflow if customized, but it would be beneficial to have an option for a warning message popup when renaming a status to ask if the admin also wants to update the transition name to align with the status update on associated workflows.

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