JIRA Automation Script - how to persist or reindex issue in script

[William Crighton [CCC]]

I have a JIRA Software (Data Center) Automation script that does the following:

Script to take the custom field "Product" value and find the matching Component value (in the issue's project), sets the issue Component value and the issue reporter to the Component Lead

After the script executes I have a followup action which generates a notification to the issue reporter.

The problem is when the automation script executes the changes to the issue made by the script are not 'picked up' by the subsequent automation component which generates the notification. The notification is set to the issue reporter set before the automation activity starts.

How can I 'persist' the issue changes made during script execution so the notification is sent to the 'new' issue owner (the component lead) when the second automation component is run?

NOTE: the changes made to the issue by the automation script _are_ persisted to the database - after the issue is created (automation script listens for issue creation) the issue component is set correctly and the issue reporter is updated to the component lead. The problem is that the notification is sent to the actual issue reporter, not the person the issue reporter is updated to during the automation script execution. And it's not the standard 'new issue' notification, it's the custom notification defined in the automation rule.

[Radek Dostál · Accepted solution]

This is what the 'Re-fetch issue data' is for:

[William Crighton [CCC]]

That's exactly what I needed! Thanks man!