JIRA can be very efficient, but out of the box not real automation exists..
If the "earlier days", the only way to do this was JellyScript - a horrible XML implementation of scripting, java wrapped in XML..
Interfacing
These days several other ways exist:
| Script/Type | Comments |
|---|---|
| Atlassian CLI | My favorite, used in Making a free JIRA Scheduler |
| JIRA JellyScript | Se atlassian (old) samples at: https://confluence.atlassian.com/display/JIRA/Jelly+Escalation |
| Groovy | Supported by the Script Runner plugin - This should be very good, made by Jamie Echlin |
| REST/SOAP API | Interfacing with JIRA through webservices |
Scheduling
The internal JIRA Scheduler via Services really sucks - only setting is a "pr. minute" count, and this:
- Resets when JIRA is restarted
- Is relative from JIRA Start, so You can schedule "at midnight"
Hence, use another Scheduler if the timing must be right, lige my Making a free JIRA Scheduler or TheScheduler Plugin
Or create Your own....
Hiding Auto Transitions
Often, You want the Automation and the User to perform the same transitions, or the Scheduler to do extra "invisible" stuff, - a hre You can:
Create an "automationservices" group
Create a Transition that can only be done by users in that group:
Hidden:
Setting fields correctly:
