Jira automation - linked issues

[Dorthe Knight]

I have a global automation rule to auto update linked issue type tasks when the Fix Version/s is updated.

It works well. However, I would like to restrict the automation to only work on a subset to tasks. The tasks I want updated are all in another Jira project and can be identified either by the key or a specific word in the summary.

I am using the if condition and have the below for both:

• stories (or other issues in epic) 
• All link types:

I have tried to add an additional JQL condition being:

summary ~ Implementation

However, this despite in the validation finding issues is stopping the rule from triggering.

Any ideas?

Regards Dorthe

[Ashley Hudson · Accepted solution]

Hey @Dorthe Knight ,

That looks like a great automation! My suggestion in this case would be to create a branch rule / related issues which can catch if the label is what you've marked in the summary! This way is way easier as you can also automate the creation of the labels if you have a pre-defined list of what "categories" the ticket would fall under and would hopefully simplify the definitions! 

Let me know if you need further clarification on this! Hope it works! :)

Kind Regards,

Ashley Hudson

[Dorthe Knight]

Hi Ashley,

I am not sure I fully understand. 

I already have a branch condition and what I am looking to do is to enhance this one so that only issues type task is updated if the summary contains implementation.

Now as the tasks are created from another automation I can add a unique label to the tasks which is not used in the trigger issue (epic). However, I am little skeptical that it will work as the summary did not.

I wonder if Jira in the branch condition is still looking at the trigger issue and not the content of the issue being updated by the automation.

Regards Dorthe

[Ashley Hudson]

So adding it to the existing automation would look like the following:

- Add the unique label for the tasks in the other automation that you have. 

- Then for the existing automation, add at the end of the automation the if matches the label "xxx" then edit fix versions / update.

- I'd then suggest to have the branch condition look at the issue updated by the automation previously, as then it creates more of a concrete sequence of events.

I've used labels to do this previously so it certainly works! Let me know how you get along :)

Kind Regards,

Ashley Hudson

[Dorthe Knight]

Thank you - I will test with my global admin when they are back as I do not have editing permissions to global automation

[Dorthe Knight]

Finally got it working - seems something in the project needed a change to be able to read from the linked issue.

Thank you for your suggestion.

In effect my only first solution also worked once that change were made: summary ~ Implementation