Epic link trigger equivalent for TMP automation

[Tina Leszkiewicz]

Hello!

I'm attempting to build an automation in a team-managed project where the trigger is the parent link being set to a specific parent (parent name = Testing).

The problem I'm running into is that there doesn't appear to be an equivalent function for "epic link" within the automation section for TMPs. Would anyone have an idea of how to build/format this trigger? Or if there's a place where I can test the epic-link automation as if it were to run in a company board?

Eventually, the automation will be run on a company board, but I need to test it out and demo it to my supervisor before he makes changes to a high-profile company board (so there's a lot of pressure on me to make sure it's correct).

Thanks!

[Trudy Claspill · Accepted solution]

Hello @Tina Leszkiewicz 

If the automation rule is ultimately going to be run against a Company Managed project, then you need to get a "test" Company Managed project to develop the rule against.

Even if you get a rule working against a Team Managed project, that doesn't mean the same rule will work against a Company Managed project.

So, do you need an automation rule for this scenario for a Company Managed project or a Team Managed project?

[Tina Leszkiewicz]

Hi @Trudy Claspill !

I didn't realize that I had authorization to even create a company-managed project, which is good to know now. In that case, I would like to build the automation for the CMP. 

There are some other components to the automation that I've already managed to figure out via my TMP, but my main concern would be the trigger for a specific Epic. Would an epic name be considered the same thing as an epic link? 

[Tina Leszkiewicz]

Here's the tree as I have it built currently. The automation is executing (not failing) but for some reason, it doesn't seem to be working. 

I rule I am trying to create is:

• When a story is created in a project that has the epic link "Testing" and a set due date, 2 subtasks will auto-populate.

I took the majority of the settings from my TMP, where the automation ran perfectly. The only fields that I added to this tree were the project name and the epic name components, but for some reason, adding those stop the automation from working 

[Tina Leszkiewicz]

Nevermind! I figured out what the problem was. Instead of using the component for epic name = Testing, I changed the component to a JQL for epic link = Testing. 

Thank you!