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

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!

1 answer

0 votes
Nick Menere Community Champion Oct 18, 2017

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.pngThis 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

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  

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. 

Any thoughts on the above @Nick Menere.

Thanks for the help.

Hi @Nick Menere any chance you look this up?

Thanks

Hello @Nick Menere any feedback is appreciated.

Thanks for the help!

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 Community Champion Nov 06, 2017

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]

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

449 views 7 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you