Triggers continue to fail creating subtasks within stories in an epic

Question

Hello, I've tried to create rules to auto-populate subtasks within stories found within an epic that contains a string and has certain labels associated with the issue. My rule keeps failing, and I've tried using the "contains" condition with and without case matching. I've created a simpler rule to auto-populate it with just using the epic name but that is also failing. I've confirmed that the epic name and epic link are the same, so I'm not sure why this trigger continues to fail?

Trudy P Claspill · Answer

@Nina Hua It will say at the bottom of the navigation pane on the left if your project is Company Managed or Team Managed.

Looking at your rule the trigger is

"When issue is created"

So, this rule will be created each time is an issue is created.

The next item is a Condition:

"When Epic Name contains...."

The Epic Name field is used only in Epic type issues, and only when those issues are created in a Company Managed project. That field is not used for Epic type issues in Team Managed projects.

If the issue created was not an Epic in a Company Managed project, where the Epic Name field contains the specified text, the rule will stop right there.

Then you have another Condition:

"Labels contains any of..."

Assuming at this point that the issue created was an Epic and its Epic Name field contained the required text, this condition will then check the Epic's Labels field. If that field doesn't contain one of the specified Labels then the rule will stop running.

The next item is an Action:

"Then: Create 9 sub-tasks"

If your rule is still running at this point

* the created issue was an Epic
* the Epic was created in a Company Managed project so that the Epic Name field would be not-empty and contains the specified text
* the Epic's Labels field contains one of the specified Label values

...then the rule will create 9 sub-tasks directly in the Epic.

This doesn't sound like it matches your intention which you stated as creating sub-tasks within Stories that exist in an Epic.

What action do you want to trigger this rule? If you are trying to create sub-tasks in Stories that exist in an Epic, then triggering it based on the Epic being created won't work. The newly created Epic won't have any Stories in it.

We need a better understanding of the scenario you are trying to automate. Please list out the steps you would go through if you were executing the scenario to create everything manually. Then indicate the parts you are trying to automate.

Nina Hua · Answer

Hi Trudy & Alex,

Would you mind clarifying the differences between a company managed project vs a team managed project. Also, please find cleaned up screenshots of the rule. Even with simpler rules with a single condition (epic name containing a string), I'm continuing to see stories fail to meet the rules (no action is performed because the story didn't match the condition).

Alex Koxaras -Relational- · Answer

@Nina Hua hi!

We are going to need a bit more information to help you. As Trudy said:

* Audit log
* Rule screenshot with components