Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to link an issue in a non-'next-gen' project to an epic in a 'next-gen' project?

Deleted user Oct 29, 2018

We want to make use of the new roadmap features in a next-gen project. However we cant link issues to epics from other non-'next-gen' projects. From the next-gen project is seems you can only create new child issues or link existing ones already defined in the same next-gen project.

If we try to link the child issue from the project in which its exists then when you search for the epic it displays its name as 'unlabelled-KEY-01'. If you attempt to link to it then you get the error - Issue 'KEY-1' must be of type 'Epic

2 answers

0 votes
Deleted user Jul 17, 2019

Has anyone been able to find a solution to this?

The same happens for me. Is there any workaround?

My plan was to track epics in a next-gen project to make use of roadmaps but then create individual tasks in existing projects and just connect them to these epics.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events