You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Jira Data Center 9.1.1
Automation for Jira
I want Automation to create a task on the 2nd Tuesday each month, and transition that task immediately to 'Ready to start next' (this is because I use the Kanban Backlog view, and I have a 'Ready to start next' as my leftmost Kanban column)
In summary: At this scheduled time (2nd tuesday) > create issue > and transition into 'ready to start next'
The 'Scheduled' Trigger points me to this doc: Construct cron expressions for a filter subscription | Jira Software Cloud | Atlassian Support
I can see I can do something like "'TUES#2' (or '3#2') means 'the second Tuesday of the month'."
However, when I enter the following...
0 0 0 ? * TUES#2
...as my 'cron expression' in the 'Scheduled' Rule Trigger I get an error: Invalid day-of-week name: 'TUES'
So I changed it to this (following the documentation):
0 0 0 ? * 3#2
...and Automation then complains "The rule has been configured with components that require issues to be provided by the trigger. You need to use the option to run JQL to provide issues. The following components require issues: Transition issue"
I'm not sure why
0 0 0 ? * TUES#2
Doesn't work, as the docs do clearly show that should work. But yeah, I used your second expression and it got past the error about the cron expression.
As to your other error, I'm guessing it might be because you are not using a "Branch" for your transition action, and so Automation doesn't know what issue to transition.
What you need to add after the Create issue step is:
And then within this branch, you would put your Transition action.
It should look something like this:
Out of interest, @Darryl Lee , whilst we're here: do you happen to know where the Automation Audit Log is stored? I'm asking because I can seacrh it only by date: on a system that has a lot of rules firing and people not putting very descriptive names for their rules, it's quite time-consuming to track down the rule in question. If I know where the Audit Log is stored then I'll see if I can at least search by both date & time as well as the issuekey to help me find the rules faster.
Hey @Arnold - you got it. The 'transition issue' rule needs to know what issue you want to act upon.
So with a scheduled trigger (which doesn't specify an issue, unlike other triggers), if you don't put it within the branch like I specified, it doesn't know which issue you want to transition.
As for finding logs for a specific rule, when you open a Rule for Editing, if you look beneath Rule details you'll see Audit log. This is a filtered view of the Log scoped to just this rule.
When I'm debugging a rule, I will typically leave the Edit screen up after Publishing changes, so I can quickly view and/or refresh the Audit log after testing.
There's a great HOWTO on doing this here:
Hey @Arnold - after testing if you find that the branch rule did the trick, could you please click the green "Accept answer" button up there? Thanks.
BTW if you didn't want to wait until Feb 14 to see if this rule does the job of creating and transitioning, as the Debugging tips above suggest, you could temporarily replace the Scheduled trigger with a Manual one. I use this all the time.