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

Move Parent Issue, when Child Issue (Epic) is moved to another status

Daniel Hamann_4owj72

Hello,

i've created mulitple issutypes above the epic.
The Complete Hierarchy is: "Ebene 2" > "Ebene 1" > "Epic" > "Task" > "Sub-Task

The Connection / Link in between "Ebene 2" and "Ebene 1" is via "parent link".
The Connection / Link in between "Ebene 1" and "Epic" is via "parent link".

I want to reach that if a certain "Epic" which is connected with an issue in "Ebene 1" is moved from one status to another also the related Parent Issue in "Ebene 1" is moved to the next status.
How can i get the Parent in "Ebene 1" with a correct branching?

Accepted answers

Stefan Salzl

Hi @Daniel Hamann ,

As I interprete your description it seems you are working with advanced roadmap. Is that right?

Best
Stefan

Mark Chaimungkalanont

Unfortunately branching / looping though the "Parent link" field is not yet supported https://codebarrel.atlassian.net/browse/AUT-1779

All comments

Mark Segall

Hi @Daniel Hamann

I believe this would work:

TRIGGER: Issue Transitioned
CONDITION: Issue Type = Epic
BRANCH: On Parent
- ACTION: Transition Issue

However, I'm not 100% whether parent is actually looking at the parent field or some kind of hard coding against epic. So if that fails, you could try an advanced branch against {{issue.parent}}

Daniel Hamann_4owj72

At first thank you very much for your quick response.

Sadly none of the two options worked. i guess it's because the triggered issue isn a sub-task. because both branches just seem to work with the child issue beeing a sub-task.

Do you maybe have another idea?

Stefan Salzl

Hi @Daniel Hamann ,

As I interprete your description it seems you are working with advanced roadmap. Is that right?

Best
Stefan

Daniel Hamann_4owj72

Hi Stefan,

yes exactly that’s right!

Stefan Salzl

As far as I know the issue hierarchy is not extended through advanced roadmap which means the created „structure“ is not detected as parent known from standard issues.

To be honest I‘m not that proficient with advanced roadmaps but I think I remember a question here in the community where this was discussed.

Best
Stefan

Mark Chaimungkalanont

Unfortunately branching / looping though the "Parent link" field is not yet supported https://codebarrel.atlassian.net/browse/AUT-1779

Daniel Hamann_4owj72

Is there any prospect, that this will change in the near future?

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-cloud

hierarchy

automation