Forums

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

Automation For Jira - Execute Rule Based On Change

Raynard Rhodes
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 9, 2018

Currently we have an automation that will create an issue in a separate project if the component is added.

 

Initially we had an issue that if the component/s field is updated, additional issues are created in that separate project. We removed the JQL "component = OTHER-PROJECT" and added compare {{fieldChange.toString}} equals OTHER-PROJECT. I've changed equals to contains and the issue still persists.

 

This works when modifying the component with one option at a time. If I'm just entering OTHER-PROJECT into component it will work. But if I put OTHER-PROJECT,THIS-PROJECT the rule will not run because the field was had two strings

 

 

I am looking for a way to make it so regardless of how many components are added at a time, they will create a new issue if it's the first time. Also if components is updated then a new issue will not be created.

 

assistance.png

 

0 answers

Suggest an answer

Log in or Sign up to answer