How to configure rule that creates subtasks when a story is created under a certain epic?

[Sebastian Brunet]

I am trying to configure automated rules in my project, but cannot seem to get the simplest rule to work. I see that it fires, but the intended actions are not taken (i.e. subtask creation).

The flow looks like this:

Trigger - Issue Creation

Issue Fields Condition - If Epic Name contains 'X'

Branch - For Current Issue

Then - Create a new subtask with parent == current issue

When I create a story under Epic 'X', I expect to see a subtask created but I do not. This flow makes sense to me logically, but clearly I am missing something. 

[Bill Sheboy]

Hi @Sebastian Brunet -- Welcome to the Atlassian Community!

Context is important for many rule actions, particularly for creating subtasks.

As your your trigger issue is apparently the Story, there is no need to branch.  For example:

• trigger: issue created
• action: re-fetch issue (I recommend always adding this action after the Issue Created trigger to prevent timing problems / errors.)
• condition: issue type equals Story
• condition: the parent Epic is what you expected
• action: create a subtask (The parent will automatically be the trigger issue without the branching.)

Kind regards,
Bill

[Sebastian Brunet]

Thank you Bill. I implemented the logic you proposed, but still do not see the desired action being taken. When I look to the trigger event (story creation) I see that the rule did in fact run, but the subtask creation never occurs. Here is the new step-by-step.

When: issue creation

Then: Re-fetch issue data

Issue Fields Condition: Issue type equals story

Issue fields Condition: Epic name equals 'X'

Then: Create subtask(s)

[Bill Sheboy]

Please post an image of your complete rule and an image of the audit log details showing the rule execution.  Those may provide context to help explain what you are observing.

[Sebastian Brunet]

The issue condition that fails is the matching to the epic name I have entered. I think I have tried every combination of match (exact, contains, etc.) and epic name, so I am not sure where the issue lies.

[Bill Sheboy]

The Epic Link, Epic Status, and Epic Name fields are being sunset, a change which started in 2023 and which continues now: https://community.atlassian.com/t5/Jira-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562

And so it is possible your issue does not contain a value for Epic Name.  The Summary field is now used in place of Epic Name.

Please examine the Summary for your Epic and adjust your condition to search that field.