Deliverable has to close when all epics under deliverable are closed.

[Kishore D]

I have requirement to create automation rule which will be working like closing the deliverable when all EPICs under that deliverable are closed. 

I am not able to fetch the epics under deliverable in automation rule. is this possible with any functions like ChildissuesOf or parentissues ?

Can i get help on how to create this Rule?

[Muhammad Moazzam Hassan]

Yes, It can be possible. I am sharing the rule which I triggered on a Schedule basis and you can trigger it on a transition basis.




First we have to verify the issue type is epic

Then check whether its parent exists

Then Go in to the Parent Via Branch

then find all the epics under the parent via JQL, in this jql I am finding those epics who are not yet closed and if any of that found the rule will run, but in your case the size must be 0 means the all epics are closed.

Then transition the PArent to Closed.

[Kishore D]

Thanks @Muhammad Moazzam Hassan ,

I tried to implement this rule. But while adding jql condition for closed epicssize 0, my jira server doesn't show JQL issues greater than condition..  JQL condition drop-down is having only 

_ Are not present

_all match specified JQL

_None match specified JQL

_some match specified JQL

JQL condition with JqL return issues count matching is not supported.. is there any way I can modify at JQL area to complete this request

[Muhammad Moazzam Hassan]

Can you share the screenshot?

[Muhammad Moazzam Hassan]

[Muhammad Moazzam Hassan]

Then use Lookup.

[Kishore D]

Hi @Muhammad Moazzam Hassan ,

I have used lookup and created Automation. I can see Automation  Rule is triggering and success but Deliverable is not closing. 

Audit log is showing the Epics closing log. But there is no log related to deliverable.
Automation Rule is as below 

[Bill Sheboy]

Hi @Kishore D 

What is the issue type of your child issues of the Epic?

As written, your lookup issues action is using JQL to find any Epics which are children of the Epic.  Instead I believe you want your JQL to use:

issueType != Epic

Kind regards,
Bill

[Kishore D]

Hi @Bill Sheboy ,

My project is having deliverables as parent link and under deliverables, epics are there.

Example: Deliverable1 is parent link, epic1,epic2,epic3,epic4 are child issues which are created with parent link as Deliverable1.

Now my automation rule has run and close Deliverable1, whenever epic1, epic2 epic3 epic4 are closed.

Above rule mentioned in screenshot is executed but Deliverable1 is not closing.

[Bill Sheboy]

Please post an image of the audit log details (Show More) for when the rule runs.  That may indicate what is happening.

I recommend using a screen print, browser addon, or screen capture tool rather than taking a photo of the screen.  That will make reviewing the image easier.  Thanks!

[Kishore D]

Hi @Bill Sheboy @Muhammad Moazzam Hassan ,

Due to some limitations, i can upload photo only. I am attaching the Audit log of rule when i close the epic.
In screenshot,   XYZNG-52 is epic. when i close the epic audit log message is as in screenshot. But there is no message for XYZNG-50 (Deliverable).

So my requirement is not fulfilled. I can see epic (XYZNG-52) closing message. But not parent (XYZNG-50 -Deliverable) close.

XYZNG-50 , Deliverable is parent and XYZNG-52 is child (epic)

[Bill Sheboy]

Hi @Kishore D 

Were you able to post that image of the audit log details?  Thanks!

[Muhammad Moazzam Hassan]

1. Just do one change as your status name is done, not Closed ao edit the jql query and replace closed with done

[Kishore D]

Hi @Muhammad Moazzam Hassan ,

Thanks for helping.. I tried that but it's still not working. 

Actually i see "AND: Parent Exists" condition is not working. 
That is reason Rule is successful but not giving results.

[Muhammad Moazzam Hassan]

What is your issue hierarchy?

[Kishore D]

It's Deliverable-->Epic-->story,task,subtask,Bug...

[Muhammad Moazzam Hassan]

Then seems like there is a difference in automation of jira server and cloud

[Kishore D]

So this is not possible in data centre?

Mine is jira data centre 

[Muhammad Moazzam Hassan]

I think this is a bug, you can contact Atlassian Support for that.