My guess is that each loopback transition is an authorisation of some sort from a different person or group each time (hopefully protected with conditions to stop the wrong people using them, and keep the display looking simple).
Each of these transitions would need to record that they have been done somehow (usually, people will do this by setting a custom field, but a better way would be a scripted field that reads the history of the issue to check the transitions have been performed)
Then your close option can be protected by a simple condition on the transition, or even performed by a listener that can pick up and check when the last transition gets done!
While the workflow sure looks scary, I’m unsure what your question or goal actually is. I might start with getting rid of all (most?) of the loop-transitions in your workflow.
Thanks for the update.
1. I have used script only, faced some issues while implementation.
2. if we run the script directly using the issue key, it is working fine.
but when added in sil listeners, auto transition not happening, may be need to try adding the script in all transition Postfunction on the particular status.
It is not clear what you are now asking about, sorry.
Could you explain where you are stuck, and exactly what you are doing?
Thanks for the support.
It is little complicated, used automation rules instead of script, now it is working fine.
It looks like you're new here. Sign in or register to get started.
