Issue Summary

When a Jira status is renamed or translated, there is a synchronization failure where the Workflow Editor and JQL continue to reference the untranslatedName (original name) while Automation rules and SLA configurations use the updated name. This results in a fragmented user experience where JQL queries must use a different status name than the one displayed in the global administration or used in automation.

Steps to Reproduce

1. Create a status in a specific language (e.g., Portuguese: "Aguardando").
2. Add this status to a workflow and publish it.
3. Rename the status globally to another language (e.g., English "Awaiting").
4. Set the User Profile language to English.
5. Observe the status name in the Workflow Editor.
6. Attempt to run a JQL query using the new English name: status = "Awaiting".
7. Attempt to run a JQL query using the original name: status = "Aguardando".

Expected Results

All Jira components (Workflow Editor, JQL, Automation, SLAs) should consistently use the current name of the status based on the user's language settings. JQL should accept the current English name.

Actual Results

• The Workflow Editor continues to display the original Portuguese name.

• JQL returns "The value 'Awaiting' does not exist for the field 'status'" and only accepts the original Portuguese name.

• Automation and SLAs correctly use the new English name.

• REST API shows name: "Awaiting" but untranslatedName: "Aguardando".

Workaround

Renaming the status in the workflow editor to a temporary name, publishing, then renaming back and publishing again sometimes forces a sync, but this is not feasible for organizations standardizing hundreds of statuses across many workflows.