Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation rule error when adding a release version trigger

Jeff Kranking March 15, 2022

When adding the following automation rule I get the error "The following components require issues: JQL condition" However I clearly have a jql condition present as shown below. What am i missing here?

 

image.png

1 answer

1 accepted

0 votes
Answer accepted
Jack Brickey
Community Champion
March 15, 2022

Right after your trigger add a branch component "for issues fixed in version". See if that gets you there.

Jeff Kranking March 15, 2022

Thanks @Jack Brickey - i was able to publish with that change but I'm now getting the following error when triggering it. 

 

`Can't branch rule as it requires issue(s) in the context for this option. More than likely you have a trigger that doesn't insert issues into the rule chain. e.g. Scheduled rule not running a JQL query. Creating an issue does not put an issue into the context, you have to branch on it directly.`

 

Not sure what im missing here. 

Stefan Salzl
Community Champion
March 16, 2022

Hi @Jeff Kranking ,

If the branch already set directly after the trigger and the error still shown on the trigger please try to change the trigger and just set it again to version released. I ran into this issue several times that the trigger needs to be changed (even if to same trigger again) to be able to save the changes.

Best
Stefan

Jeff Kranking March 16, 2022

Got it working with using the branch component - "for issues fixed in version". I just deleted the whole rule and then recreated and the "Can't branch rule" error went away. Thank you for the help  @Jack Brickey @Stefan Salzl 

Like Stefan Salzl likes this

Suggest an answer

Log in or Sign up to answer