Trying to write an automation rule that is triggered when a specific story is moved to a status

[Raina Anand]

I want to create a rule to create more issues under an epic but we only want that to trigger once one of the previous tickets named (summary)  "Finalize ticket price" is moved to done. How should I set up the conditions and trigger? 

[Suraj Aderogba]

Hi @Raina Anand 

That’s a great use case and one you can handle neatly with Jira Automation.

Here’s how you can set it up step-by-step:

Your Goal: Automatically create new issues under the same Epic when a specific Story (with summary “Finalize ticket price”) is transitioned to Done.

Automation Setup: 

1. Trigger: Issue transitioned

Set it to trigger From any status → To Done (or whichever status represents completion in your workflow).

2. Add a “Condition → Issue fields condition”

Choose Field: Summary

Operator: contains

Value: Finalize ticket price

(This will ensures the rule only runs when that specific story is moved to Done.)

3. Add a “Branch rule / related issues”

Select “Epic (parent)”

This action will makes the automation act on the Epic that contains the story you just closed.

4. Inside the Epic branch, add an “Action → Create issue”

Choose the same project and issue type (e.g., Story, Task, Sub-task, etc.)

Use the Epic Link or Parent field to automatically link the new issues to that Epic.

You can predefine the summary and description of the new issues, for example:

Summary: Review release documentation

Description: Automatically created after "Finalize ticket price" is completed.

Example of a simple working Rule Flow

Trigger: Issue transitioned → Done

   → Condition: Summary contains "Finalize ticket price"

       → Branch: On Epic (parent)

            → Action: Create issue(s) under that Epic

This setup ensures the automation only fires once the specific story “Finalize ticket price” is moved to Done, and then automatically creates your new issues in the correct Epic.

I hope this helps. 

Suraj . 

[Bill Sheboy]

Hi @Suraj Aderogba 

As a reminder, when posting bot / AI-generated content, ensure you post the source of that content.  To learn more, please review the community guidelines for appropriate use of such tools:

https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement

Kind regards,
Bill

[Bill Sheboy]

Hi @Raina Anand 

What have you tried thus far to solve this?

When you have a rule that is not working as expected, please post the following the provide context for the community to help:

• an image of your complete rule
• an image of the audit log details showing the rule execution
• explain what is not working as expected, and why you believe that to be the case

Until we see those...

Is your "Finalize ticket price" issue a child issue of the Epic where you want to add more children?

Kind regards,
Bill

[Raina Anand]

Yes it is, I hadn't created the rule when I posted this question, didnt really know how to get started, so Ill post what I have now 

I will try the above solution unless you have any specific suggestions to this. 

[Bill Sheboy]

Thanks for that image, @Raina Anand 

You rule is close to the solution!  Please move the Story create inside of the branch, setting the Epic Link to the "current issue" so it is a child of the Epic.

[Raina Anand]

Perfect! Thank you so much

[Raina Anand]

Should I move the re-fetch in & the add watchers section in too? @Bill Sheboy 

[Bill Sheboy]

Perhaps; let's review what the rule does to decide:

A re-fetch action refreshes the data for the trigger issue, but your rule is not changing the trigger before that point...thus it is unclear why there is a re-fetch.

To which issue do you want to add the Watchers: the trigger one, the Epic, etc.?  Knowing that will help decide what is needed.

[Raina Anand]

We want the watchers added to the new story thats being created, would I open another branch for 'Most recently created issue' ? 

[Bill Sheboy]

No, that will not work because branches cannot be nested.  Let's try some edits to your rule, moving the issue create outside the parent branch and using a smart values

• trigger: issue transitioned to Done
• condition: project equals YOURPROJECT
• condition: issue type equals Story
• condition: summary contains...
• related issues condition: check that a parent Epic exists
• branch: to parent
  • action: transition the issue
  • action: add comment
• action: create issue, for the new Story
  • for the Epic Link field, enter this smart value in the field
    • {{triggerIssue.epic.key}}
• branch: to most recently created issue
  • action: add watchers

I add the Related Issues Condition so the rule will only continue if there is a parent Epic.