Automate (creation, and) assignation of Parent issue upon Story creation

[Kevin Zelechoski]

Greetings, y'all!

I've been searching this forum, but am not finding the answers I need. Using creation of a new Story as the trigger - how can I use an Automation to:

• designate a pre-existing Epic as Parent for that new Story; OR
• create a new Epic and designate as Parent for the new Story (when the Epic doesn't already exist)

I'll be happy to take questions and provide further context; thanks in advance for any insights the forum can provide :)

Respectfully,

Kevin Z.

[Trudy Claspill]

Hello @Kevin Zelechoski 

Welcome to the community.

Another couple of points need clarification.

You say you want to designate a pre-existing Epic as the new Story's parent Epic and create a new Epic and designate that as the Story's parent Epic. A Story can have only one parent Epic.

Do you have some criteria that you will use to tell you to link the Story to a pre-existing Epic vs. creating a new Epic?

Also, are you working with issues in a Team Managed project or a Company Managed project?

[Kevin Zelechoski]

Hi Trudy, 

Thanks for engaging with me here.

I've amended the description from AND to OR; my intention with 2b is to account for scenarios where an Epic to serve as Parent doesn't already exist. 

I expect the criteria for linking the Story to a Parent Epic will be a tag-based field (e.g. Labels); still TBD.

We are working in a Company-managed Project.

[Mark Segall]

Hi @Kevin Zelechoski and welcome to the community!

A few questions:

1. What is the trigger for your issue creation (manual, scheduled, based upon another issue transitioning, etc.)?
2. What is the business logic that would determine what epic it should be tied to and...
3. What is the business logic to determine that the epic exists or not?

[Kevin Zelechoski]

Hi Mark, 

Thanks for your questions.

The trigger for Story creation is manual.

The logic to determine the intended Parent epic is likely to be the presence of a common tag in a field like Labels; I haven't determined how to account for the scenario where the Epic (to serve as Parent) doesn't yet exist.

[Mark Segall]

So let's walk through this a bit more, you're on issue ABC-123.  You click automation and then select your manual rule to execute... What happens next? 

• Does it create a clone of the issue that triggered the rule? 
• Does it create something entirely new?

Think of Automation like an RPA.  If you were doing this manually, what steps would you be taking?  This will help us formulate the rule.