You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
Hi,
For my project I have 2 project
- a next-gen project for high level roadmap
- a 'normal' scrum project with improvements/new feature/sub tasks
When I open a issue in my scrum project, it seems that I cannot select an epic of my next-gen project as epic. Is this correct?
I can add the issue of my scrum project as link on the next-gen epic, but this is not what I want.
Greetings,
Dieter
Hello @Dieter_Lauwers
Possible duplicate
Please see the following answer from Petterson Goncalves (Atlassian)
Hello Robin,
Unfortunately, you can not link issues that are not from a next-gen project with Epics from a next-gen project because this kind of Epics does not have an Epic-name. That's why it is being displayed as unlabelled.
I agree with you that it can cause some confusion. If it's intended that classic issues should not link to Next-gen Epics, it should not even display as an option in the Epic Link field.
That's why we opened a bug to fix this behavior and allow the link between both issue-types:
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.