Hello Team,
I usually create epics for bugs for various products that my company produces.
I don't want the epic to close when I close all the bugs (which are task and sub tasks) under that epic.
Can I form a rule specific to issue type i.e., Bug?
To prevent the closing of an epic based on its child issues (both sub-tasks and regular issues), the best approach is to use a workflow validator. Alternatively, you can try Automation, but keep in mind that while Automation can't prevent a status change, it can revert it back to the previous status.
There is no out-of-the-box validator for such case, therefore we've developed the Linked Issues Validator available as part of the Workflow Building Blocks for Jira app. With a wizard-like UI, you can select options that represent your case. You can choose relations from: sub-tasks, parent issues, stories, children, and linked issues. Additionally, you can filter relations by issue types and select criteria based on status category and status
In your case, the "Children" option would be the best, as it tests both regular issues and sub-tasks under the Epic.
I am leaving a link to the app's documentation if you are interested.
I hope it will help.
Cheers
Hi Sushmita,
t's more the other way around. Epics do not get closed by themselves and one would need an automation to close them.
So best check the automations that can run for you project and disable those.
Cheers,
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you mean to restrict - prevent closing of the epic ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.