All Epics with 100% Done filter to mark as done

Question

Hello,

I am trying to search for all Epics that all child tickets are done and the Epic is 100% done, so I can mark the Epic status as done.

It seems that the field progress is not searchable.

Much appreciated!

coolcodeiguess · Answer

with Script Runner:

NOT issueFunction in epicsOf("status != Done")

Charles Wahab_r6zwof · Answer

Thanks @Mark Segall - i'll give the rule a try!

Ste Wright · Answer

Hi @Charles Wahab

Can I clarify if...

* You just want to locate all Epics which have done children (no automated transition)? Or...
* You want the Epic to auto-transition when all children are Done?

---

(1) Find Issues

This isn't possible using native JQL, as it does not support sub-querying (i.e find Epics based on logic at the Children level) - your options are either...

* Automation: Use Automation to populate a field at the Epic-level, which you can refer to using native JQL* Create a Custom Field to highlight when all child issues are "Done" - eg. a Checkbox Field
* Use Automation to populate this Field, based on child Issues being transitioned, created, etc

* App: Use an App from the Marketplace, which would provide the ability to use JQL sub-queries - for example...* JQL Search Extensions for Jira
* Enhanced Search
* ...or another option from the Marketplace

---

(2) Auto-Transition the Epic

If you'd like to automate the Epic's transition, you could use Automation for this.

Mark has provided one option in another answer. The alternative is:

* Trigger: Issue Transitioned* To Status = Done

* Condition: Issue Fields Condition* Field = Issue Type
* Condition = does not equal
* Value = Epic

* Branch: Related Issues* Type = Epic (parent)* Branch-Condition: Related Issues Condition* Related Issues = Stories (or other issues in Epic)
* Condition = All match specified JQL
* JQL = status = Done

* Branch-Action: Transition Issue* Destination Status = Done

---

A few notes on the rule in (2)

* This only checks the next level down - Story-level - it does not take into account Sub-tasks which might still be open below the Stories, Tasks, etc.* You'd need to consider how to handle this if required - eg. Post Functions to stop a Story being closed if it has an open Sub-task, automating the closure of Stories, additional Conditions in the above rule, etc.

* You should also consider a Rule to reopen an Epic if relevant - i.e if a Story is reopened, or a new Story is added to a closed Epic - should the Epic reopen also?

---

Let us know if any of these options work for you :)

If you'd like more information, or detailed instructions for how to create the Automation Rules recommended in (1) or the notes for (2), also let us know so we can advise further!

Ste