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

Move to status only when a subset of linked issues form one proyect are "Done"

Sebastián Delmastro

I have a Issue form project A that have several linked issues form A, B and C projects.

Those linked issues can be tasks, incidents or bugs and also can be linked to an epic.

Suppose I have a1, a2, a3 status form project A and also other statuses for B and C (b1, b2, c1, c2, etc)

I want a rule that automatically move the A issue from a1 to a2 when only one of his linked B issues are moved from b1 to b2. Also I want to move A to a3 when ALL of his B linked issues are on b3 status.

BTY b3 = "Done"

Thanks!

Accepted answers

All comments

Nick Menere

Hi Sebastián,

I've seen this use-case a few times.

Start progress when the first linked issue moves to In Progress.
Close an issue when all linked issues have been closed.

The first rule would look like:

Screen Shot 2017-10-19 at 3.37.32 pm.png

This rule does the following:

When an issue transitions to "In Progress" in project B
Find the linked issue in project A
If it is in "To Do"
Transition it to "In Progress"

The second rule would like:

Screen Shot 2017-10-19 at 3.42.15 pm.png This rule does the following:

When an issue in project B is transitioned to Closed
Find the linked issues in Project A that are "In Progress"
Check to see that all linked issues back to project B are Closed
Transition the issue to Closed

Hope that all makes sense.

Cheers,

Nick

Sebastián Delmastro

Thanks @Nick Menere since you are referencing the trigger issue ({{issue.key}}) in the related JQL issues and conditioning them to be present or not on the project and status condition,
It is necessary to check via smart field the "linkedIssues({{issue.key}})" clause?

Given that you are checking issues to be en B project and status in the related issues of the branched linked issues?

I am trying thos now.

Thanks

Sebastián Delmastro

It is not working @Nick Menere

This is the rule:

Captura de pantalla 2017-10-24 a la(s) 10.20.39.png

This is my 2 JQL conditions for linkedissues:

Captura de pantalla 2017-10-24 a la(s) 10.22.47.png

Captura de pantalla 2017-10-24 a la(s) 10.31.40.png

This is the error message from audit log

Captura de pantalla 2017-10-24 a la(s) 10.33.25.png

Any help and comments is appreciated.

Sebastián Delmastro

Any thoughts on the above @Nick Menere.

Thanks for the help.

Welcome!

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

Quick Links

Find more posts tagged with

jira

addon-com.codebarrel.addons.automation