You can use Golive with ScriptRunner for Jira, here are some inspirational use cases.
Groovy Scripts Examples
You can search and update Golive data using Golive Java components in custom groovy scripts. These scripts can then be used by workflow validators, postfunctions, listeners or any other ScriptRunner components.
In order to remove repetitive "boiler plate" code, we strongly advise you to structure your groovy code into small re-usable classes.
Example: update attributes of an environment
Script example to get an Environment and update its attributes:
This script depends on com.apwide.golive.helper.EnvironmentHelper and com.apwide.golive.accessor.EnvironmentServicesAccessor groovy classes
(you can copy code from tabs above).
Files must be structured that way in your script root:
In this example, we update the issue Summary with the list of Environments selected in an Environment Custom Field. As the custom field returns a list of Environment IDs, we use the Golive CustomFieldType to get the Environment names:
Environments added in the field "Environment(s) to book" are added in the Summary
In this example, we automatically select the target Environment in our Change Requests (Jira issues), depending on the type of change defined in the "Promotion Path" field (Production Fix, Change Request, Enhancement).
For that, we have created a ScriptRunner Listener: