I have a script that should transition issues returned by a JQL query. The transition that should be performed is a GLOBAL transition (workflowTransitionUtil.setAction (201) ).
Actually the script works well in the Script runner interface, executing this global transition on the issues.
But it don't run when I put it in Service. When I put another (non global) transition, it also works well as a Service.
How can I get the global transition running as a Service?
Thanks for support!
Could solve the issue by removing conditions from the global workflow transition. I had the conditions: Status not open/closed. But I can remove this conditions and cover this by adapting the JQL query in the script: "AND NOT status in (Open, Closed)". I still use the "hide transition" condition which is working fine :-) (Actually I cannot explain why the conditions mentioned above made problems when I put the script as a service (but not when running the script through the script interface))... Thanks anyway!
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs