I have requirement that I am trying to fulfil using ScriptRunner. Only send emails on issue update when issue is in certain statuses. We have a 'Planned' status for issues and Assignees shouldn't get bombarded with emails while in this status. Once it progresses to the next status, "Active" (or other statuses) the assignee should get emails when the issue is updated. I have this all setup using a custom event being triggered by a Script Listener (Fire event when condition is true). It works great, very simple. The only problem is that the email received doesn't contain the correct "changed" information.
It's like the custom event is fired before the issue is indexed or all the context to compute the changed values isn't transferred through the Script Listener.
Any assistance would be appreciated. Is it a ScriptRunner bug? Is it a limitation of Jira?
It is possible that when you created this event to be triggered in the workflow in Jira that the order of operations are such that the issue is transition to a new state, then the event/email is generated, and then the indexes are updated.
I would recommend checking the specific workflow in question, and then check on this transition in question. From there check the order of the workflow. I would certainly want to make sure that Jira has reindexed the issue before trying to trigger this scripted event. It is a pretty common thing to see when creating new post functions in workflows in Jira, they tend to be created at the top position. For the sake of data accuracy, and giving the indexes a chance to update, in this case it's probably going to need to have that event near the bottom of the post functions.
Hi all! My name is Miles and I work on the Marketplace team. We’re looking for better ways to recommend and suggest apps that are truly crowd favorites, so of course we wanted to poll the Community. ...
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