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

Portfolio "Parent Link" and issue types - inconsistencies as field is for all issue types?

Markus Dieterle

Hi all,

the Portfolio field "Parent Link" is locked so it is available for all issue types, I cannot change that.

So I put it only on the Epic Screens - ok so far.

Problem: When user change the issue type from Epic to Saga (Moving an issue), the field field Parent Link is not updated, as it is also available for issue type saga. A user is not even able to map it during the move process, it just does not show up at all during move.

Bad Consequence: We have Sagas in our instance which have a parent link to another saga. This should not be possible and and leads to problems. Even Jira prompts this inconsistency with a Warning in the issue search, see screenshot "This link is inconsistent with your Portfolio hierarchy"

Any ideas if this is works as designed and what can be done to prevent that?

Comments

miikhy

Hi Markus,

Definitely agree with you: it's confusing!

The thing is that, as Jira sees the field available in both types, it's not prompting to remove it while moving the issue. The only option I could imagine would be to subscribe to a filter returning all Sagas with parent links so that you can bulk change them on a regular basis. There are Apps which can also help (automate a transition at precise frequency, that automation could empty the parent link).

Would any of those help?

Cheers

Markus Dieterle

Hello Micky,

thank you for your thoughts.

so that you can bulk change them on a regular basis.

This bulk change would consist of actual 3 bulk changes, right? (Move back to epic, remove parent link, move back to saga)

As bulk change parent link for saga is also not possible:

But yes a subscription is a good idea to at least know the issues.

Still not really a satisfying solution on large instances.

Wondering why this inconsistency seems to be work as designed, or if I should report it as a bug.

Best regards,

Markus

miikhy

Hello Markus,

Agreed! Bulk change won't work in a single step as your screenshot shows! That quite a pain! An alternative could be a script (based on either ScriptRunner or PowerScript) which can be ran at a stable frequency and will check all Sagas for Parent Link values and clear them. That being said, it implies external addons

As per your last question, or remark, Portfolio is adding another dimension to Jira and the fact that portfolio defines a new hierarchy is the exact reason why Jira (not portfolio) sees that as work as designed. Jira's not considering the Parent Link field differntly when moving an issue whereas when editing the field it seems to be considering Portfolio hierarchy. Youcan still create an improvment feature on Atlassian's Jira, it will follow the usual process of selection but you should not expect a quick workaround as there are many requests coming from every customers!

Hope this helps!

Welcome!

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

Quick Links

Find more posts tagged with

developer

hierarchy

advanced-roadmaps