如何配置规则：关闭epic前需先关闭所有子任务

Hey there! Let’s work through fixing this Epic closure restriction— I’ve tackled similar configurable workflow rule issues before, so here’s a breakdown of the most likely culprits and how to resolve them:

1. Double-Check the Rule’s Trigger Event & Timing #

First off, make sure your rule is set to trigger specifically when the Epic’s status is being changed to a closed state (like "Done" or "Closed"). A common mistake is setting the rule to trigger on any "update" event without narrowing it down to the status transition to closed. If the rule isn’t firing at the right moment, it can’t enforce the restriction.

• Verify your trigger condition explicitly includes: Epic Status = Changing to [Your Closed State Value] (match the exact status name used in your system).

2. Validate the Sub-Task/Child Item Query Logic #

This is where most issues crop up— your rule needs to accurately find unclosed child items linked to the Epic:

• Confirm your query filters are correct: It should target items where Parent = Current Epic AND Child Item Status != [Your Closed State Value]. Don’t mix up the status operator (e.g., using "equals closed" instead of "not equals closed") or forget the parent-child association.
• Cover all child item types: If your Epic links to multiple entity types (Stories, Tasks, Sub-tasks, etc.), ensure the query includes all of them— not just one type.
• Watch out for permission context: Some rule engines run queries using the triggering user’s permissions. If the user closing the Epic doesn’t have access to view all child items, the rule might miss unclosed ones. If your system allows it, set the rule to run with admin/system permissions to avoid this gap.

3. Ensure the Rule’s Action Blocks the Transition #

Your rule needs to do more than just detect unclosed children— it has to stop the Epic from being closed:

• Use the correct action type: For example, in tools like Jira, you’d use a "Validate Transition" rule that returns an error message when unclosed children are found. In other systems, look for a "Reject Status Change" or similar action.
• Add a clear error message: Something like "Cannot close Epic: There are uncompleted child tasks/items. Please finish or close all linked children first." This helps users understand exactly why the closure is blocked.

4. Check for Rule Priority & Conflicts #

If you have multiple workflow rules running, another rule might be interfering:

• Ensure your Epic closure check rule has higher priority than any other rules that modify Epic or child item statuses. For example, a rule that auto-completes child items could run before your check, leading to incorrect logic.
• Review rule execution order in your system’s workflow settings to make sure your restriction rule runs first.

5. Test & Debug with a Simple Scenario #

Don’t skip testing with a controlled setup:

• Create a test Epic, add 1-2 unclosed child items, then try closing the Epic. Check your system’s rule execution logs (most platforms have this) to see if the rule triggered, how many child items it detected, and if the block action ran.
• Simplify the rule first: Start with a basic version that just checks for any child items (ignoring status) to confirm the trigger and action work. Then add the status filter once the core logic is working.

内容的提问来源于stack exchange，提问作者Secret Squirrel