Automation to create stories/subtasks linked to new Epic doesn't work in Business Project?

Allison Stewart_nejvgh

Hi,

I have an automation to create stories and subtasks when an Epic is created.  This is working perfectly when I run it in a company managed software project.  But then my users don't get to easily see the hierarchy of issues and see the progress of the Epic.

But when I run this automation in my company managed (or team managed) business project, the automation will associate the sub-tasks to the stories, but won't link the stories to the Epic.

I want this:

Epic1
  Story1
    Subtask1
    Subtask2
  Story2
    Subtask1

I would like these users to have a business project because I think it's easier for them to see their hierarchy of tasks and work in a more simple manner than in a software project.  But I just can't get this automation to link the stories to the epics.

NOTE: I tried using one automation rule that creates the epics, stories and branches to create the subtasks.  AND I tried using 2 rules: one to create the epics and stories and one to create the subtasks to the newly create stories.  In neither case, can I get the stories linked to the epic.

Screenshots attached.

 

Trudy Claspill

For Team Managed projects the "Epic Link" field is not used. That is why the rule does not work for such projects.

You instead have to set the Parent field on the child story to add it to the Epic.

Refer to answers on this post for information on how to do that.

https://community.atlassian.com/t5/Jira-Software-questions/How-do-I-Automate-Client-Field-to-Associate-with-an-Epic/qaq-p/1985634#U1985645