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; } } }

How to make a OR condition in Jira Automation

serge calderara

Dear all,

I have a case where I need to close different issue related to parent issue when parent goes to a certain status

Let see the issue configuration below as an example

As you can see from parent issue above it has 2 linked type referring to different issue.

What I am trying to do is that when parent issue is transitioning to DONE, then I need to transition to COMPLETED all issue which where linked type is "Refer to Incident" and "demands"

My current rule is as below :

Any idea how can I acomplish this ?
Does the Link type accomplish a AND or OR operation ?
Do I need to add an other step ?

Thanks for clarification

regards

Accepted answers

Dirk Ronsmans

Hi @serge calderara ,

For me the Link Types there would be all the link types that will match. One link can only have a single link type so adding in all the link types that you need should act like a OR

Something like all issues where link type = demands or refer to incident

I am wondering tho if you even need to do this.

You are

1: trigger it on the parent issue when it goes to Done

2: you then check the project, why not just make a project specific rule

3: For linked issues: select an issue type -> why don't you just set the action to move them to completed under this component?

Imo, it will loop through the linked issues and you already check it in the For Linked Issues component.

Hana Kučerová

Hi @serge calderara ,

alternatively, if you have different workflows and need to distinguish between the final statuses, you can do it like this:

I agree with @Dirk Ronsmans , but I've already had this picture prepared, when I found out there's his answer , so I decided to post it instead of throw it away :-)

All comments

Dirk Ronsmans

Hi @serge calderara ,

For me the Link Types there would be all the link types that will match. One link can only have a single link type so adding in all the link types that you need should act like a OR

Something like all issues where link type = demands or refer to incident

I am wondering tho if you even need to do this.

You are

1: trigger it on the parent issue when it goes to Done

2: you then check the project, why not just make a project specific rule

3: For linked issues: select an issue type -> why don't you just set the action to move them to completed under this component?

Imo, it will loop through the linked issues and you already check it in the For Linked Issues component.

Dirk Ronsmans

Something like

Unless I'm completely mistaken and misinterpreting this rule

Hana Kučerová

Hi @serge calderara ,

alternatively, if you have different workflows and need to distinguish between the final statuses, you can do it like this:

I agree with @Dirk Ronsmans , but I've already had this picture prepared, when I found out there's his answer , so I decided to post it instead of throw it away :-)

serge calderara

Thanks @Dirk Ronsmans , I will give a try and let you know

regards

serge calderara

@Hana Kučerová interresting this approach too, I will keep it thanks

By the way, I have heard that in cloud Automation there is a kind of limitation token of number of execution rules.

Is it still the case ?

If yes how do we know when a rule fails becuase of reaching the token limit ?

regards

Dirk Ronsmans

@serge calderara There is still a limit on how much components you can use

https://support.atlassian.com/jira-software-cloud/docs/what-are-service-limits/

serge calderara

dear @Dirk Ronsmans my scenario is a bit more complex here is the complete picture :

The trigger issue is as below :

As you can see the first link type is "is demanded by" which then succeed to transition the incident SD-4508 to completed. Then if I open the SD-4508 it displays as below :

As you can see from above my goal is to close also the Refer to Incident issue when trigger issue SWD-233 is set to DONE.

But as you can see it does not work ., status remains WORK IN PROGRESS L2

is below my rule :

Seems that the condition in red square above is not logically apply teh condition.

Any idea ?

regards

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud