Automation triggered multiple time

[Pierre Violleau]

Hello
I want to create an automation that create a  ticket when the "VS" component is added to another epic ticket. I can do it right now but my problem is that if I add any other component my rule will be triggered. How could I stop my rule to be triggered everytime?

[Bill Sheboy · Accepted solution]

Hi @Pierre Violleau -- Welcome to the Atlassian Community!

When you only want to create the new Epic when that specific component value was added, the fieldchange / change log smart values may be used to test that.

For example:

• smart values condition:
  • first value: {{addedfieldChange.values}}
  • condition: contains
  • second value: Adobe

This condition will pass when that specific Component value is added.

Kind regards,
Bill

[Pierre Violleau]

Hi @Bill Sheboy and thank you for your help.

To validate your solution I tried this simple rule when we change the value component for Adobe with this condition you purposed and as a result we should have a commentary.

This is not working. I think I'm missing something

-

[Bill Sheboy]

Thanks for trying that, and it appears you are using Jira Server or Data Center, thus that specific field change smart value will not work.

As an alternative, you may use the {{changelog}} smart values with two conditions, one after the other:

• advanced compare condition:
  • first value: {{#changelog.component}}{{fromString}}, {{/}}
  • condition: does not contain
  • second value: Adobe
• advanced compare condition:
  • first value: {{#changelog.component}}{{toString}}, {{/}}
  • condition: contains
  • second value: Adobe

This tests the Components did not originally contain Adobe AND it was added.

Please note well: I believe the smart value for components is singular for the change log entry, and not plural like with issues.  Please test that to confirm for your Jira version.

[Pierre Violleau]

@Bill Sheboy My hero! Thanks a lot everything is good now!

[Valerie Knapp]

Hi @Pierre Violleau , welcome to the Atlassian Community and thanks for your post.

You should be able to put a condition to listen only for the value of the Component you want to create the issue for, like this

Is this what you meant?

If it's not or you need more help, please write back and, if you can, share an anonymised version of the rule so we can try to troubleshoot with you further.

Best wishes

[Pierre Violleau]

Thanks for your help and sorry for my english this is not my first language

That was my first try but anytime after that, when the fields "component" is modified, my rule is triggered again

First I have my ticket, i add VS => OK
Then same ticket, i add xxx => rule trigger again => not ok   :)

[Pierre Violleau]

This is my current rule (in French)

[Valerie Knapp]

Hi @Pierre Violleau , thanks for the screen.

It looks like you have the trigger, then a branch? Is that correct?

I would have the trigger, then a condition, like you have. I think you could combine the two conditions you have here in a JQL one and then have the action.

I hope this helps you.

If not, @Bill Sheboy is a genius at automations, as he is here already, we are in safe hands and we will get this working for you.

Best wishes