nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation of Epic, creation of tasks, then association of epic link to newly created tasks

Patrick Hendry_xxl6x9

I am moving a service management ticket over to a software project. When moving the service management ticket, we are setting it to an epic in a software project. The jira automation I have in place is to:

When issue is moved from project A - B

AND issue type is Epic

Create A, B, C tasks

Then update A, B, and C epic link to the original epic that moved over.

I cannot figure this one out. What is also weird, I can create a sub-task that gets associated to the epic, but not a story, bug, or task.

Accepted answers

Patrick Hendry_xxl6x9

I've tried various way to get the child tickets that are created from the trigger to have the epic link to the trigger epic moving over from another project. Still no luck tying into that epic link for the child task.

Screen Shot 2023-10-30 at 11.10.49 AM.png

All comments

Patrick Hendry_xxl6x9

Here is the audit: ACTION DETAILS: ["10139"]

ISSUE CONDITION The following issues passed: FUL-309

CREATE ISSUE Issues created successfully FUL-310

EDIT ISSUE Error editing issues FUL-309 (Could not find issue by id or key. (parent))

CREATE ISSUE Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Epic Name (customfield_10011) Issues created successfully FUL-311

EDIT ISSUE Error editing issues FUL-309 (Could not find issue by id or key. (parent))

CREATE ISSUE Issues created successfully FUL-312

Bill Sheboy

Hi @Patrick Hendry -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Kind regards,
Bill

Patrick Hendry_xxl6x9

Bill Sheboy

Looking at the rule you have posted, are you trying to make the newly created Task a child issue of the trigger issue, epic?

If so, have you tried to set the epic link at the same time as the issue create? Please show an image of that rule action.

Patrick Hendry_xxl6x9

What's interesting, the sub-task type logic works fine, but I want to create tasks under the epic, not sub-tasks. Subtasks work, tasks fail.

Screen Shot 2023-10-30 at 12.18.24 PM.png

Patrick Hendry_xxl6x9

Perhaps because I'm moving the ticket and not creating a new one, the logic is trying to find the epic link for the original ticket, which in this case it doesn't have one since it's a service desk ticket being moved over to a software project and converted into an epic.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud