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

Epic/Parent Link Change Discussion

MollyJo Tighe

Atlassian seems to have not allowed comments on any of the articles about this change, so I'm starting this discussion thread!

Upcoming changes: Epic link data above the epic level

I am failing to see how removing parent links above the Epic level is a positive change. We all know projects long ago grew in most organizations to need more hierarchy than just Epic/Story, and this will now remove our ability to add in our own hierarchies and tracking in a way that's easily traceable.

This in my case breaks all our reporting, and also all my automation around Epics and their parent ticket type (since using "relates to" is NOT a solution that I can rely on for automation rules.)

I am strongly against this change, and I cannot be the only one.

Comments

John Funk

Hi MollyJo,

Can you include a link to the article to which you are referring?

MollyJo Tighe

Edited to include!

John Funk

I don't see anything in the article that says you won't be able to create a hierarchy above the Epic. You just won't be able to do that with the Epic Link field. You will still be able to have Initiatives, Themes, etc.

MollyJo Tighe

@John Funk Are Initiatives available to non-Portfolio folks? I don't seem to have these on my instance.

Sarah Wright_6i2mim

@Danno @John Funk Given a user must currently have edit rights to an epic to add that epic link to a standard issue, when the change to parent is implemented, will edit rights to the parent issue still be required? Hoping this works like the existing Parent Link and edit rights are NOT required on the issue that is becoming the parent.

Current:

Initiatives live in project I.

Epics live in project E.

Stories live in project S.

Users must have edit rights in E and S in order to use the epic Link and link a story to an Epic.

User do not have edit rights in project I and can use the parent link to select an initiative. Ideally this is how the Parent Link will work for epics in the future.

Danno

Good morning @Sarah Wright, the needed permissions won't change. There was a recent update sent out about the migration which I'll need to find for all the latest info. on how long Epic links will remain, etc.

Sarah Wright_6i2mim

Thanks for the reply!

To restate you are saying a user would still need edit rights on an epic in order to add that epic as a parent issue.

That's a bummer.

Danno

@Sarah Wright I guess I didn't understand the question. I was referring to the fact that the user would need to have edit permission in the project to edit the Epic or Task or whatever issue type you have in that project. That said I believe that one of your users in Project S would be able to link a story to an Epic in Project E just with the edit permission in project S. I have not verified this yet since it was never an issue for my company.

We usually have an Epic and add child issues to it within the Epic itself so that it is automatically linked no matter the project.

Also, to better explain the change if you have issue types like an Initiative it likely will contain multiple Epics which is where the Parent field has lived. This new setup just makes this the standard within the hierarchy. It also removes the need for an Epic Name that is separate from the summary, The parent field will use the summary to make this connection going forward.

I hope this does a better job of explaining it.

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

jira-software-cloud