Scheduled Ticket Creation + Transition

[Patrick Tresp]

Hey, 

to have scheduled tasks created automatically, we want to implement an Automation which takes care of this. Also it should be transitioned to a specific status to appear automatically in KanBan board.

For this we created following Automation:

WHEN: Scheduled ( e.g. at first Monday of month )

THEN: Create a new Task in Project XYZ ( with Assignee etc. )

AND: Transition issue to …

When saving and trying to publish we get an error:

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

What is this supposed to mean?
As far as i understand i can not execute the transition the ( just with this automation created issue ), but i have to run a query to find that just created issue and execute a search and run the transition on every found issue.

I hope this is not the case, since i sort of expected that the "create" action returns the issue itself where the transition can be executed on?

If it is the case, how should a jql query look like to find the just created issue and only this one?

i tried:
reporter ="ID OF JIRA AUTOMATION" AND status="TO DO"
which in dry run shows 0 issues found and "Run Rule" leads to "NO ACTIONS PERFORMED"

I am happy for any help, i think i have a different thinking approach how this chained automation works.

[Mark Segall · Accepted solution]

Hi @Patrick Tresp - You can bypass the requirement for JQL

[Patrick Tresp]

Hi @Mark Segall ,

Thanks for quick reply. Unfortunately i can not bypass this, because an unchecked box leads to this error where i need to run JQL queries:

[Patrick Tresp]

The transition itself is pretty default so there should not be the cause of the JQL requirement?

[Mark Segall]

Ahh - I see the problem.  There is no context to what needs to be transitioned when you get to the transition issue action.  Your rule should look something like this:

• TRIGGER: Scheduled (box unchecked)
• ACTION: Create Issue
• BRANCH on created issue
  • ACTION: Transition issue

The branch will set context on the Transition Issue action

[Patrick Tresp]

Hey @Mark Segall ,

thanks that makes sense and opens up now thinking :-)

I set it up fresh and did set it up as suggested, and it i am facing identical issue here:

So i see there is no workaround using that JQL for now? 

[Mark Segall]

You have it set to branch on current issue for which there is no context.  It should branch on "Most recently created issue" instead.  That should address the error.

[Patrick Tresp]

That was it! 


Thanks for your support on that! What a gain!