Changing how a global transition is displayed on the New Issue view

[Séverin MAZOUNIE]

Hello, 

I have a workflow with several transitions, some standard ones (Status A > Status B) and some global ones (Allow all statuses to transition to this one). I named or renamed each and every one of them so that they are as meaningful and indicative as possible for the end-user, e.g. "Start work" for the transition going from Backlog to In Progress, or "Discard task" for a global transition going from any status to Canceled. 

Now on the new issue view, in the workflow action drop-down that displays all the available transitions from the current status with a <transition name> -> <destination status> format, while the standard transition names appear correctly, e.g. Start work -> In Progress, the global transition always appear as "Transition to" -> <destination status>, e.g. Transition to -> Canceled, although those transitions have different names, e.g. "Discard task", in my workflow, and appear as such when viewing or editing the workflow as text or diagram.

This creates situations in which the user has for example 6 available transitions to choose from, 3 that are pretty clear, e.g. "Start work", "Work done", "Task blocked", and 3 other that are all named "Transition to" instead of their real names, making things quite confusing..

I checked, there is no jira.i18n.submit or jira.i18n.title properties on those global transitions.
Also, when switching back to the old issue view, the workflow button displays the real transition name correctly, e.g. "Discard task". Hence, it seems this forced "Transition to" text is specific to the new issue view.

I tried adding jira.i18n.submit and jira.i18n.title properties with my custom transition name as values on those transition with no success obtaining the expected result. 

Is there currently any way to replace this generic Transition to display name by the actual transition name? (or any other input that we can edit)

Thank you in advance for any help!

Best regards,

[John Funk · Accepted solution]

Hi @Séverin MAZOUNIE  - This is a bug in my opinion - you can find it here: https://jira.atlassian.com/browse/JRACLOUD-70203

You should vote for it and then watch it. But it's indeed the same problem with have. I have actually created a new Status called Discard to make it clearer. It's a shame that we have to add to the overhead of the system to handle it. 

[Séverin MAZOUNIE]

Hi John,

That's what I was afraid of.. Issue voted and watched, I hope that Atlassian will address this soon! although with 120+ open improvements on this new issue view, I'm not very optimistic.. That would indeed be a shame to loose core functionality and have to use less than optimal workarounds over a UX revamp.. Thank you very much for your prompt answer anyway! 

Best regards,