You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
There are often times when we want to offer our developers specific actions, which we use to enforce and simplify workflow. The way that we typically do that now is to add a transition which does not change the status, but has post actions in Scriptrunner which do any custom work.
This seems like a hack though. Some of the issues we have with this are:
1) You can not reject the "action" if the user does not provide certain fields because Scriptrunner in cloud cannot reject a transaction because it's async
2) You can't have forms for the action which contains fields which are not associated with the ticket. This results in us creating custom fields that the ScriptRunner scripts have to clear when the action is done. For example: We have our own "Create Linked Issue" transition for our projects which are not Service Desk. To create this, we needed to add a "NewIssueAssignee" field and "NewIssueLinkType" field, which the script can use to create the new ticket, but then it needs to clear them on the original ticket. This seems like a big hack, plus, because it's not necessarily atomic, you could have an issue where two people running the same action on the same ticket have colliding data. (i.e. one removes the other ones changes, or uses the wrong values in the script).
How do other people create "actions" for their users?