How to check if 2 issues are complete to then update the status of another issue

[Joseph Khalil]

Hi Everyone!

I am new to Jira and I am trying to create an automation rule where:

If issue 1 & 2 have their status to complete

THEN

issue 3 will update its current status of TO DO to IN Progress.

Every different iteration I have tried only checks to see if issue 1 or issue 2 are in the TO DO status rather than checking issue 3.  

[Trudy Claspill]

Hello @Joseph Khalil 

Welcome to the Atlassian community.

When asking for help with an Automation rule please provide the following:

1. A screen image that shows the entire rule
2. A screen image showing the entire audit log entry for when the rule was executed.

In addition to that I have the following questions:

1. Are all three issues in the same project?
2. How do you know which issue is #1, which is #2, and which is #3? Are you linking the issues together? What are the details of how these issues are related?

[Joseph Khalil]

1. The issues are in the same project

2. Issues 1 and 2 are individual issues. Where I run an IF statement to see if both individuals issues are completed. I have not added linked issues to the task that needs to be distributed.

Hope the image below assist further

[Trudy Claspill]

A rule is triggered by an action that happens. In your case your want to trigger your rule when an issue transitions to Done.

When a single issue transitions to Done that triggers the rule. At that point the only issue the rule knows about is the one issue that triggered the rule.

In order to achieve your goal you need to tell the rule how to find the other two issues of interest.

If you were doing this manually, and you transitioned ABC-1 to Done, how would you manually figure out the issues that you call #2 and #3? Describe the flow, and then we can help you understand how to convert that to an automation rule.

In the rule that you have shown there are no steps that tell the rule the identities/keys for issues #2 and #3. When we understand how you would figure that out manually then we can figure out what steps are needed to do that automatically.

[Joseph Khalil]

The following method below is how I picture it.

If you were doing this manually, and you transitioned ABC-1 to Done, how would you manually figure out the issues that you call #2 and #3? Describe the flow, and then we can help you understand how to convert that to an automation rule.

If ABC-1 was transitioned to done manually, I would first ensure that all the criteria was completed; for example if the task is to email a team member and that is completed then I would transition it to done as the task is now completed.

If task 2 is then to speak with the staff member to see if they have received the email, I would say there is a direct link between task 1 and 2 as in order for 2 to take effect, firstly the email needs to be sent. 

If task 3 was to see if they have read the email, similar to the above the email needs to be sent first...

Note that I am using issue 2 & 3 as their name for simplicity reasons as opposed to their names within the project.

Step 1:

Epic is manually created and transitions  --> In progress 

Automation Create issues --> 1 -- Where issue 1 is send the email to the staff member

Step 2:

When issue transition from In progress --> Done (as email was sent)

Create issue --> 2 & 3 (2 - check if they received the email, 3 - check if they have read it).

The above to me works in a logical manner, but what I need is the ability to see all the issues (in a backlog) to monitor the timeline as eventually issues will have a fixed due date and need to ensure they fall within scope of the project duration.

SO If I go on the basis of the following

Step 1:

Epic is manually created and transitions  --> In progress 

Automation Create issues --> 1 -- Where issue 1 is send the email to the staff member

Step 2:

Check to see if issue 2 & 3 exist within the Backlog

If they exist and if issue 1 has the DONE status assigned

Update the issue status from Backlog for 2 & 3 --> TO DO status

I hope the above shows the flow correctly. And thank you for your help so far!

[Trudy Claspill]

You mentioned that an Epic is created manually and the issue 1 is created automatically. Are issues 2, 2, and 3 child issues under the Epic?

Do these three issues always have the same Summary, with issue 1 being 'demd email", issue 2 being "confirm email received", and 3 being "confirm email read"?

We have to have a way for the automation to figure out if it was issue 1, 2, or 3 that transitioned and triggered the rule. One way to do that is to look at the contents of the Summary field, if that field will have a consistent and unique phrase in it for each issue.

Once we know which of the issues transitioned, we have to have a way for the automation to find the correct related issue. If they are children of the same Epic we can combine that with examining the Summary to put focus on the correct related issue and transition it.

If you need to see all three related issues from the start then I would recommend that you create all three at the same time.