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?
Unfortunately branching / looping though the "Parent link" field is not yet supported https://codebarrel.atlassian.net/browse/AUT-1779
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Daniel Hamann ,
As I interprete your description it seems you are working with advanced roadmap. Is that right?
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe this would work:
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}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.