Sidehistorik
...
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't schedule "at midnight"
Hence, use another Scheduler if the timing must be right, lige like tweaking my Making a free JIRA Scheduler or buy TheScheduler Plugin
Or create Your own....
Hiding Auto Transitions
Problem
Often, You want the Automation and the User to perform the same transitions, or the Scheduler Automation to do extra "invisible" stuff, - a hre You can:This can be tricky, also because any validations not handled in the transitionscript will cause a fail:
| 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
...