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!

[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:

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:

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:

This is my 2 JQL conditions for linkedissues:

This is the error message from audit log

Any help and comments is appreciated. 

[Sebastián Delmastro]

Any thoughts on the above @Nick Menere.

Thanks for the help.

[Sebastián Delmastro]

Hi @Nick Menere any chance you look this up?

Thanks

[Sebastián Delmastro]

Hello @Nick Menere any feedback is appreciated.

Thanks for the help!

[Sebastián Delmastro]

Any news @Nick Menere?

Haven't got any feedback from you. Maybe is better to create a support ticket. I have the impression codebarrel guys try to respond but they don`t do the follow up. It happend to me in other community questiones i have raised.

[Nick Menere]

Hi Sebastián,

Sorry but we answer everything we see. There might be an issue with us receiving notifications of replies. 

The first problem I see is the JQL will produce incorrect syntax.

{{triggerIssue.status.name}} = "To Do"

This would produce something like:

To Do = "To Do"

This isn't valid Jql.

This should be:

status = "To Do"

This is why you are getting the first error.

Bu then you have the opposite jql in the next condition - "status != "To Do"

So I am not sure quite what you are after.

Hope that makes sense, and again, sorry for the delayed response.

Cheers,

Nick Menere [Code Barrel]