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.
Dear colleagues, I would like to write an Adaptavist script that sends an eMail notification whenever any issue in a project reaches a well known state. I'm using a "Listener" for this, bound to the "Any Issue Event" event in the respective project.
Success so far:
Sending eMail on any issue event with $issue.key etc. values in eMail text
Send eMail only if issue in status "blah". Condition: issue.status.simpleStatus.name == 'blah' (I omit the ?. operator on purpose because issues are supposed to have a status).
No success (eMail does never get fired): originalIssue.status.simpleStatus.name != 'blah' && issue.status.simpleStatus.name == 'blah'
What do I do wrong? Any help welcome
although I do not want you to neglect the approach with listeners in any way I just wanted to mention we used the "Send a custom email" function during a transition.
The listener might be a better choice if you have a very detailed set statuses you want to match (and additionally not being specific to a workflow).
In case the scenario is much simpler the approach with "Send a custom email" tied to a transition (in one specific workflow) might suffice.
Example use case over here was to send a customized mail to recipients listed in a field of type "multiple user picker" through an "approve" transition (informing them that the specific issue has been approved). That works pretty good.
Basically this is used as an alternative to the introduction of a new event (and perhaps an additional velocity template).
In summary: the distinction if this can be applied to your use case is by the question if you have several workflows or if it only should apply to a specific one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.