This may not even be possible, but I'm trying my hardest to make it work.
We love the "Roadmap" feature of the next-gen project, however, the lack of customized workflows is a no-go for migrating fully. We have too much automation setup in our workflows.
So, I was trying to try to have the best of both worlds. We set up a next-gen project with only epics. In our original classic project, I tried to add "Parent Link" to the issue view from the field configuration. And it looks like in the configuration that I can add it. However, when I go back to the issue, I don't see the linking ability at all.
Is there maybe another setting or something to make this show? Or maybe this isn't even possible and I can continue to dream.
Hello again @Shane
Sorry for misguiding you here. Let me correct myself.
For classic, the epic links are created from the 'Epic Link' field OR by dragging an issue card in the backlog on to an Epic in the 'Epics panel' (left sidebar):
For Next-Gen projects, you are able to add Epic links (parents) from the dropdowns you are looking at AND from the breadcrumbs:
I don't mean to be rude, but it doesn't seem like you read my original post. I am trying to add "Parent Link" to an issue in the classic project. I know about Epic Link, but I can't use this for Epics that are in next-gen projects.
It doesn't seem like it's possible, however. So we will not be using a next-gen project, because of the huge lack of functionality of next-gen projects, per my original post.
🤦♂️Oh dear. You are very right. I'm sorry for that.
As you say, "Parent Link" as it works within next-gen projects is not a feature available to Classic projects. Let me dig a little into the why:
- Classic projects have a very structured (and limited) issue hierarchy: epics, issues, subtasks. Epics are a 'special' type of issue, which is where the Epic Link and other features come from
- Next-gen projects are built on a foundation of configurable hierarchy, where any issue type you define can be parent to any issue type you define. Long term, this hierarchy will be fully configurable. This is the reason for the links between issues and 'epics' in the current next-gen projects are done throught the 'Parent Link' relationship.
You are right to point out that you cannon link a nex-gen Epic to a classic issue in the classical sense of Epic linking (where you see the relatioship directly reflected in issue breadcrumbs and epic level summaries.
However, I believe you could work around the issue by creating a new issue link type: 'is parent of' for example. That way, you could 'Link issues' with the standard linking:
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events