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

Can't change Parent issue when an issue is assigned to it via Parent Link

Sergio Montávez

Hi,

Given an issue creation (regular User Story, not a sub-task) I want to update its parent using Jira Automation rules. Situation:

I have 2 issue types: User Story and Dummy
Dummy is in the leve above User Story
User Story issue types can be assigned to Dummy issue types using the Parent Link field

The goal is to update the status of the Dummy ticket when a User Story is created but I cannot find the way to do so. I've already tried out rules based on Issue linked Child-task of and When issue created (US) and Branch rule / related issues for: Parent but neither of them are working.

Do you know how to update a Parent issue type when its child is not a sub-task?

Thank you!

Accepted answers

All comments

John Funk

Hi Sergio - what do you mean by Dummy is the level above User Story? Outside of an Epic not such parent level exists.

So, have you just linked the issues using a particular link type?

Can you share the rule that you have so far?

Sergio Montávez

With Atlassian Advanced Roadmaps package, you can add new issue types to any hierarchy level and also add new hierarchy levels. So, I've added a new issue type (Dummy) to the same level of Epic so issue types in the level of Story can set this Dummy issue type as their Parent issue via using Parent Link field (a field provided by Advanced Roadmaps), see the image.

hierarchy levels.png

The procedure to set them as their parent issue is the same as assigning an issue to an Epic, but using Parent Link field instead of Epic Link field.

Unfortunately, I've tried several rules and I've discarded all of them, don't have a record of them right now.

Thank you

John Funk

But you have to decide what type of link the parent link will use. Usually something like Blocks or Depends On.

What are you using between Master Epic and Epic?

Sergio Montávez

Mmm not exactly since this parent-child relationship is stablished differently, let me explain that with some pictures.

As you can see, for the Issue JOE-19 I have two fields: Epic Link and Parent Link. Parent Link is how you tell JOE-19 that it belongs to parent issue JOE-32.

Then, in JOE-32 issue you have this visualization of which are the issues that have it as a parent issue via Parent Link hierarchy, which is different from the feature "Link issues" that you mention.

JOE-19 issue (child):

JOE 19.png

JOE-32 issue (parent):

JOE 32.png

Precisely because they are not linked as you mentioned is why the Jira Automation rules that I mentioned don't work for this parent-child relationship through Jira Advanced Roadmaps.

Coby Fuller

From my experience with Advance Roadmaps so far, I was able to create a new issue type (Initiative) one level above an Epic, and was able to add the 'Parent Link' field to all Epics. Now I can link an Epic directly to an Initiative (now parent of the Epic). Since the Epic issue type is unique and typically would not have a sibling at this level, my best guess is that the 'Epic Link' field is the only Parent/Child link available at this level, thus the 'Parent Link' is technically not available at this branch of the hierarchy.

Sergio Montávez

Hi @Coby Fuller

You are able to establish a Parent/Child relationship at the Epic level with non Epic issue types as Parents and also the "Parent Link" field works in that way as my PoC uses this relationship. Additionally, when using the API rest you can see that relationship is feasible, you can even retrieve some related data in the Automation rule.

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