Any suggested workaround for UI issues with looping transitions & fast track transitions in JIRA 9?

[Chris Pentz]

We're currently evaluating JIRA 9 and the new transition button is causing some problems with how we use looping transitions and fast tracks from scriptrunner.

(Looping transition is just a transition that transitions from itself to any status)

(Fast-tracks are just listeners that transition automatically if conditions are met)

Example:

- We create a looping transition called "Resolve" and has a screen associated with it

- Based on the info filled out in it, we use scriptrunner fast-track listeners to forward it to the next relevant status, which can be different based on the values filled out

Problem:

Looping transitions in the new JIRA 9 transition drop-down, always show the action + the destination status... and for looping transitions that means the status it's already in.

In our case, we don't want to show it going to the existing status, we just want to show the action (as it was in JIRA 8 and earlier).

I see no UI configuration options for this and the alternative is creating a ton of transitions in our workflows, which will get messy to say the least as we have several of these fast track looping transitions. (so users can focus on actions, rather than statuses)

I would be nice if could use scriptrunner fragments to simply create our own buttons to trigger the transition screens, but I can't find any api docs on how to do this.

Looking for suggestions!

[Chris Pentz]

Hi Ram, the problem does not lie in the fast-track transition, but is entirely a UI issue:

So an example of this is our resolve transition which we setup to use from any status:

Previously this would show in JIRA 8 as a simple resolve button:

which now looks like this in JIRA 9 (which will confuse our users):

As for the fast-track transition, it would depend on what the user fills out the following screen that determines how to route it. i.e resolution = fixed go to status A, if resolution = will not fix, go to status B, etc. etc. etc.

It's been a great solution to keeping our workflow simple.

Now the only solution I can think of is to make fake statuses that match the transition names and use forwarding on those, but this will make our workflow quite messy and has potential to cause confusion as well:

In an ideal world these looping transitions wouldn't show the destination status.

[Ram Kumar Aravindakshan _Adaptavist_]

Hi @Chris Pentz

Could you please provide a screenshot of your Fast-Track transition configuration and the code you use?

I am requesting this so I can review it and provide a solution.

Thank you and Kind regards,

Ram