Let's presume we would like to trigger a sync back once the issue has been exalated and modify our issue in some way.
Let's say we would like a Mood custom field to be set to 'Happy' and a description of an issue to be 'Created from the Script Runner'.
In order to achieve this one can easily, configure a custom Script Listener to subscribe to EXALATED Jira event.
This can be done as follows:
- Install a Script Runner plugin for Jira:
- After a successful installation navigate to the Script Listeners section of the Script Runner plugin:
- Then pick 'Custom listener' from the list. This will take you to the page where you can actually create your custom listener:
- Pick up the desired project from a dropdown list and choose a 'com.exalate.api.domain.trigger.EXALATED' event type from the list:
Next step would be to write your custom listener script. It is written using Groovy language. Here's an example of such a script
The actual implementation can change depending on the JIRA version.
courtesy of Glenn Verrijkt
- Save the listener. Now we're ready to go! navigate to an issue which you'd like to exalate and perform an Exalate operation:
- Now let's wait until the synchronization is performed (there is a lozenge on the right side which indicates the state of the synchronization):
- Once the issue has been exalated - let's refresh the page and check whether the changes got applied:
We can see that the Mood has been changed to 'Happy' and the description has changed as well.
This is all it takes for one to create a custom event listener for EXALATED event and start integrating Exalate into your Jira at a brand new level.