Introduction
This documentation site provides a lot of example scripts containing approaches on how to implement various use cases. Many of these scripts are meant to illustrate how challenges can be resolved and are not meant as the solution for the issue you try to resolve.
Examples
Script / Usage article link | Purpose | Supported Platforms |
|---|---|---|
| Used to synchronize Versions | JIRA SERVER JIRA DATA CENTER | |
| Components.groovy | Used to synchronize Components | JIRA SERVER JIRA DATA CENTER |
ExalateEventListener.groovy DEPRECATED This approach has been deprecated. Use these methods instead: Updating a local custom field with a remote issue key in Exalate for Jira on-premise Updating a local custom field with a remote issue key in Exalate for Jira Cloud Syncing a comment with a remote issue key in Exalate for Jira on-premise Syncing a comment with a remote issue key in Exalate for Jira Cloud | The script allows subscribing to Exalate Jira issue events:
| JIRA SERVER JIRA DATA CENTER |
Status.groovy (Server) Status.groovy (Cloud) | Used to synchronize Statuses | JIRA SERVER JIRA DATA CENTER JIRA CLOUD |
| IssueLinks.groovy | Used to synchronize issue links | JIRA SERVER JIRA DATA CENTER |
| Move.groovy | Used to move issues automatically | JIRA SERVER JIRA DATA CENTER |
| CustomFieldSync.groovy | Used to synchronize custom fields | JIRA SERVER JIRA DATA CENTER |
| SubTask.groovy | Used to synchronize Sub Tasks | JIRA SERVER JIRA DATA CENTER |
Epic.groovy (Server) Epic.groovy (Cloud) | Used to synchronize Epics on Jira Server/ Jira Data Center | JIRA SERVER JIRA DATA CENTER JIRA CLOUD |
| TempoWorkLogSync | Used to synchronize Tempo Worklogs. | JIRA SERVER JIRA DATA CENTER JIRA CLOUD |
SimpleSprintSync.groovy DEPRECATED Use how to synchronize sprints on Jira to configure sprints synchronization. | Used to synchronize Sprint field | JIRA SERVER JIRA DATA CENTER |