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; } } }

Jira Work Management: Epic Parent Link in Task Missing

Rachael Axtman

Hi! We are working on setting up an automation where a set of tasks will automatically be associated to the parent. When we run the automation it does not work and says the following message:

Could not find your configured field, it may have been deleted?

Parent Link

How do we connect the children to the parent in an automated way? We do have script runner as well if that's a possibility, but not sure of the restraints because this is a Jira Work Management project.

Screenshot 2023-09-28 at 11.34.19 AM.png

Accepted answers

Trudy P Claspill

Hello @Rachael Axtman

Is this automation applying to issues in a Team Managed project or a Company Managed project?

You said "Epic Parent Link" in your title. Can you confirm that you are trying to make a standard issue type (i.e. Story, Task, Bug) a child of an Epic?

Can you show us the complete automation rule?

Atlassian has been making some changes to which field is used in a child issue to track its parent Epic in an effort to standardize functionality. You may be getting tripped up by those changes. Answers to the above questions will help us figure that out and give you the guidance you need.

All comments

Trudy P Claspill

Hello @Rachael Axtman

Is this automation applying to issues in a Team Managed project or a Company Managed project?

You said "Epic Parent Link" in your title. Can you confirm that you are trying to make a standard issue type (i.e. Story, Task, Bug) a child of an Epic?

Can you show us the complete automation rule?

Rachael Axtman

Hi @Trudy P Claspill

It is a team-managed Work Management project. This type of project when created does not have the ability to be company managed.

The automation is:

-When an issue type of Epic is created

-Then create a new task in the project with a set summary, blank description, and linked epic link to the issue.

We tried:

-Using the Epic Link field and having it "Copy Epic Link from Epic Issue"
-Using the Parent Link field and having it copy the parent link field from the parent issue
-Using the Parent Link field and having it copy the trigger issue

None of those seemed to work. I'm hoping there is something that I'm missing

Trudy P Claspill

1. Copying either Epic Link or Parent Link from the parent issue won't work. If the parent issue had those fields then they would be used to record the parent of the parent (the grandparent) of the issue you are creating.

2. The same is true, in this case, with copying from the trigger issue because the trigger issue is the Epic you want to set as the parent of the task you are creating. This is effectively the same my 1.

You will need to use the More Options feature in the Create Issue action and edit the field using JSON.

{
  "fields": {
    "parent": {"key": "{{triggerIssue.key}}"}
  }
}

Rachael Axtman

Thanks @Trudy P Claspill Trying that out now

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud