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

How do you prevent an Epic from closing until all Stories are closed?

James Gray_f8ayds

I'm trying to create an automation that prevents the closure of an Epic, if all of its Stories are not closed. I've been following this post Stop Epic from closing if unresolved stories/tasks but I am not sure how to go back and call the Epic ticket's custom field to update it, once all the stories are closed.

I have it so that the automation checks to the epic to ensure it has a story, that has transitioned to done, where it then adds a value to the custom field. Now I need to set it so that, once all the fields have a value of 1 or once all the statuses are set to done, it then allows the Epic to close.

I'm not looking to add an app if at all possible.

Thanks!

Accepted answers

Trudy P Claspill

Hello @James Gray

It would've been helpful if there were images in the post you were referencing, as you have gotten a little off track.

In the step where they say " if: Stories match Status..." they are referring to using the If:Related Issues condition.

Screen Shot 2023-08-11 at 7.03.32 PM.png

That gives you the necessary fields to create the condition they described.

Screen Shot 2023-08-11 at 7.03.50 PM.png

Screen Shot 2023-08-11 at 7.06.49 PM.png

All comments

Trudy P Claspill

Hello @James Gray

It would've been helpful if there were images in the post you were referencing, as you have gotten a little off track.

In the step where they say " if: Stories match Status..." they are referring to using the If:Related Issues condition.

Screen Shot 2023-08-11 at 7.03.32 PM.png

That gives you the necessary fields to create the condition they described.

Screen Shot 2023-08-11 at 7.03.50 PM.png

Screen Shot 2023-08-11 at 7.06.49 PM.png

Sanjog Sigdel

Hi @James Gray

I've implemented the following condition:

My workflow for story transitions ticket from Approved-Ready for Prod -> Done. I have this condition:-

The ticket can only be marked as Done when it's subtasks are completed.

I did that using the Validation and Condition in workflow transition. It was handled without any automation.

Maybe this will help in case of EPIC without using Automation.

Stefan Salzl

Hi @James Gray

I would suggest a combination of "setting a custom field" within your Epic (that was suggested in your link) and a workflow condition.

The reason for this is that an automation rule cannot avoid a transition. The transition will be done and the automation rule could revert this afterwards. A workflow condition is the way to go if it comes to blocking transitions.

regarding the automation rule:
- whenever a story is closed/done and a parent (Epic) is linked
- forEpic all stories are checken if done
- if all done --> set field to 1
- if not --> keep 0
then add a condition to the workflow transition that checks against your custom field and only allow this transition to be done when the value equals 1.

Hope this was helpful. Please let us know if you have any further questions.

Best
Stefan

James Gray_f8ayds

Hey @Sanjog Sigdel

I have that same validation/condition set up for my subtasks, however, I'm trying to create one for Stories now, but that doesn't seem to be the default option under the same validation/condition settings. I think the workaround is going to be a customer value field.

James Gray_f8ayds

Thanks for the suggestions,

I followed your flow, and I had to change the original condition, it didn't seem to trigger when using "Is not one of", so I changed it to "Is one of", and seems to be performing correctly!

Maciej Dudziak _Forgappify_

Hi @James Gray

I would propose an alternative solution using a validator. I am from Forgappify, and we developed the Linked Issues Validator, which can greatly simplify blocking parent-child relationships.

community_05.19_children.png

Choose the 'Children' or 'Stories' options and the status category in which child issues need to be in order to allow the transition.

I would appreciate it if you could give it a try.

Cheers

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-core

automation

jira-service-management-cloud

jira-service-management