How do I create separate automation rules to automatically close issues?

[jacob.aicher]

I have a very simple Jira project setup where I have Epic, Story, and Sub-task issue types. My process is as such:

1. I create an Epic
2. I create one to many Stories under the Epic
3. Each Story may have one to many Sub-tasks under it

I currently have an automation rule the will automatically close the Story when all Sub-tasks are marked Done. 

I'm expecting that the same rule would fire for the Story to Epic relationship, but it's not happening. 

I'm thinking that I may need to create a separate rule in some capacity but I'm getting a little lost and hoping someone can help me. 

[Trudy Claspill · Accepted solution]

Hello @jacob.aicher 

Welcome to the Atlassian community.

To help you debug your automation please provide the following information.

1. A screen image that shows your entire rule.

2. A screen image that shows all the details from the Rule Details page.

3. Describe the scenario where you expect/hope the rule works to also close Epics.

One thing that may be affecting your scenario is that the rule may not be getting triggered if it is the rule that causes the Story to be closed.

There is a checkbox on the Rule Details page that you have to check if you want the rule to be triggered by actions that are completed when an Automation Rule executes.

If that box is not checked, and the rule is triggered by the transition of an issue, then when the rule is initially triggered by transitioning a subtask, and the rule then closes its parent story, the transition of the parent story will not retrigger the rule to assess if the parent epic should be closed.

[jacob.aicher]

Hello @Trudy Claspill 

Thank you! Happy to be here. Below is a screenshot of the of the rule setup. I used a template for this and made no adjustments.

Here's a screenshot of the Rule Details.

Your explanation is now making sense. This rule is working the way I desire for my Stories. Whenever I close all Sub-tasks that live under a Story issue, the Story automatically closes. 

This is the same functionality I am looking for when it comes to all Stories closing underneath of an Epic and having the Epic automatically close.

---

After testing out the use of "Check to allow other rule actions to trigger this rule", the rule is now working both for Sub-tasks closing Stories as well as Stories closing Epics. So thank you for this! This resolves my issue!

One additional question I do have for you, if you can answer it here. Is it possible to separate these into two different rules to save on the amount of triggers? We have limits that get reached on a monthly basis and I'm hoping that separating them into two separate rules would allow for them to be triggered less often, if that makes sense. 

[Trudy Claspill]

Usage is not based on a rule simply being triggered. 

For information on how usage is calculated refer to this document:

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

The only time this rule will count against your usage is if the Transition Issue action is actually executed.

A Jira Admin (Product Admin, Site Admin) or an Organization Admin for your site can examine the Automation Usage information to see which rules are being counted against it.

https://support.atlassian.com/cloud-automation/docs/view-your-automation-usage/

[jacob.aicher]

Thank you for these details, @Trudy Claspill !