I am trying to sync the status of linked issues. However, there is a scenario which I can't avoid to sync the wrong issue. Following is the scenario * The Scope setting is All projects. * There are three projects. * Project A * Project B * Project C * There are four issues and all issue types are Task.* A-1 (Project A) * A-2 (Project A) * B-1 (Project B) * C-1 (Project C)* A-1 is the main issue which include all information * A-2, B-1 and C-1 all [relates to] A-1 Following is the steps * When B-1 or C-1 transition the status to Done * Check if C-1 and B-1 status are both Done. if not, do nothing. if yes, transition A-1 status to Done but A-2 should not transition to Done Currently, I can't avoid A-2 transition to Done in this scenario. Does anyone know what condition I should put after this automation triggered. Please give me your input. 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; } } }

Sync [relates to] issues' status by automation

unknown

I am trying to sync the status of linked issues. However, there is a scenario which I can't avoid to sync the wrong issue. Following is the scenario

The Scope setting is All projects.
There are three projects.
- Project A
- Project B
- Project C
There are four issues and all issue types are Task.
- A-1 (Project A)
- A-2 (Project A)
- B-1 (Project
- C-1 (Project C)
  - A-1 is the main issue which include all information
  - A-2, B-1 and C-1 all [relates to] A-1

Following is the steps

When B-1 or C-1 transition the status to Done
Check if C-1 and B-1 status are both Done. if not, do nothing.
if yes, transition A-1 status to Done but A-2 should not transition to Done

Currently, I can't avoid A-2 transition to Done in this scenario. Does anyone know what condition I should put after this automation triggered. Please give me your input.
Thank you

Accepted answers

Paul O_qqk8km

You could try using a related issues condition as shown below. For your project A, I've used project ACME and for projects B & C, I've used SP and SUP.

This seems to produce the desired results.

Screenshot 2023-06-03 at 19.14.33.png

All comments

Trudy P Claspill

Hello @[deleted]

Is there a relates to link between A-2 and the issue (B-1 or C-1) that transitioned to Done?

Your Branch is looking at the issues linked to the trigger issue (B-1 or C-1) by the relates to link.

It is then checking if that linked issue matches the JQL project in (B, C) and status = Done. That is not a check confirming that the B-1 and C-1 issues are in a Status of Done.

If the linked issue (linked to the trigger issue B-1 or C-1 by the relates to link) matches the JQL (in project B or C and already set to a status of Done) then it will transition the linked issue to the status of Done.

So, I'm not sure how this rule could be changing the status of issue A-2.

Can you provide the rule's Audit Log details for the execution that changed the status of A-2 to Done?

unknown

Hello @Trudy P Claspill,

Thank you for your reply.

Is there a relates to link between A-2 and the issue (B-1 or C-1) that transitioned to Done?

->No, Only B-1 or C-1 transitioned to Done will trigger this automation

It is then checking if that linked issue matches the JQL project in (B, C) and status = Done. That is not a check confirming that the B-1 and C-1 issues are in a Status of Done.

-> if so, what JQL I should put after branch relates to if I'd like to check both linked issues of project B and project C are both in a status of Done.

Thank you

Paul O_qqk8km

You could try using a related issues condition as shown below. For your project A, I've used project ACME and for projects B & C, I've used SP and SUP.

This seems to produce the desired results.

Screenshot 2023-06-03 at 19.14.33.png

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