Sidehistorik
JIRA Jira can be very efficient, but out of the box no real automation exists..In the "good old 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 |
|---|
, used in Making a free JIRA Scheduler - and can | Automation App | Almost standard now-a-days... (and You get it automatically in cloud) Some Apps, like JSU App and Script Runner App offer parts of automation |
| Atlassian CLI | Can be "integrated via shell calls from script, powershell and other programming languages. As it is java based, it is virtually platform independant, the main downside is that is is slow. |
| JIRA JellyScript | See Atlassian (old) samples at: https://confluence.atlassian.com/display/JIRA/Jelly+Escalation |
| ||||||
| Script Runner App | See some samples at library.adaptavist.com |
Supported by the Script Runner plugin - This should be very good, made by Jamie Echlin
See sam samples at https://jamieechlin.atlassian.net/wiki/display/GRV/Miscellaneous+Groovy+Scripts| REST API | Interfacing with JIRA through webservices - REST, The SOAP and XML-RCP is deprecated |
...
Scheduling
The internal JIRA Scheduler implemented in Services really sucks - only setting is a "pr. minute" count called delay, and this:
- Resets when JIRA is restarted
- Is relative from JIRA Start, so You can't schedule "at midnight"
Hence, use another Scheduler if the timing must be right, like tweaking my Making a free JIRA Scheduler or buy TheScheduler Plugin
Or create Your own....
Hiding Auto Transitions
Problem
...
| Kodeblok |
|---|
2014-05-05 22:46:30,674 QuartzScheduler_Worker-3 INFO ServiceRunner CloseResolvedIssues [jira.jelly.service.JellyService] JellyService.run 2014-05-05 22:46:30,803 QuartzScheduler_Worker-3 ERROR anonymous CloseResolvedIssues [jira.jelly.service.JellyService] file:/pack/jira-jelly/support-closeresolved.xml:48:125: <jira:TransitionWorkflow> The following problems were found: customfield_12922: ITIL Tag is required. org.apache.commons.jelly.JellyTagException: file:/pack/jira-jelly/support-closeresolved.xml:48:125: <jira:TransitionWorkflow> The following problems were found: customfield_12922: ITIL Tag is required. at com.atlassian.jira.jelly.tag.JellyUtils.processErrorCollection(JellyUtils.java:24) at com.atlassian.jira.jelly.tag.issue.TransitionWorkflow.doTag(TransitionWorkflow.java:133) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) |
...
Solution
Create an "automationservices" group
...