I would like to setup an automation rule that will have the following: * Trigger: When issues are linked * Condition: If tickets are from different projects (or one ticket (destination ticket) is not in a specific project) * Action: Edit field of destination ticket How would I do this? I am a bit confused on how the "Brach" feature works, I suspect this might be the solution. Thank you.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Trigger automation rule only if 2 tickets are from different projects

Danilo Simic

I would like to setup an automation rule that will have the following:

Trigger: When issues are linked
Condition: If tickets are from different projects (or one ticket (destination ticket) is not in a specific project)
Action: Edit field of destination ticket

How would I do this? I am a bit confused on how the "Brach" feature works, I suspect this might be the solution.

Thank you.

Accepted answers

Mark Segall

Hi @Danilo Simic - You could use the Advanced Compare condition and do something like this:

{{issue.project}}
does not equal
{{destinationIssue.project}}

The tricky part is knowing which issue is which. Will the source and destination always be the same (e.g. Project A is always blocks Project ?

All comments

Mark Segall

Hi @Danilo Simic - You could use the Advanced Compare condition and do something like this:

{{issue.project}}
does not equal
{{destinationIssue.project}}

The tricky part is knowing which issue is which. Will the source and destination always be the same (e.g. Project A is always blocks Project ?

Sarah Noor_2wx9j4

You can add in some conditions like this in the global automation rules.

Screenshot 2022-08-18 181837.png

Danilo Simic

The idea is to not trigger the rule when both tickets are from the same specific project, for example if both tickets are from Project XYZ then the rule should not trigger.

Danilo Simic

Thank you for the help. I tried this, however it does not do what I need.

Danilo Simic

I just tested this, it works. Thank you very much for the help.

Mark Segall

Just updated my previous comment as I realized I forgot the closing mustache.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation