Hi,
We are faced with the problem of linking the task of the classic project to Epic in the nex-gen project.
Case:Project A - classicProject B - next-gen
I try fill field (EPIC LINK) of Task of Project A http://take.ms/yqyXl and select Epic from Project B. In select item showed as unlabelled http://take.ms/agsgI and after select and save I receive error:Issue 'PLPAY-141' must be of type 'Epic' (http://take.ms/pEwvk)But in Project B PLPAY-141 it is Epic issue from Roadmap
What am I doing wrong?
Hello @Nick Ivlev
Currently, it's not possible to link classic project issues to Epics belonging to next-gen projects.
@Tarun Saprathanks for info 🙏
Hello @Tarun Sapra
Fo you know if linking Epics and Stories are on the roadmap?
Hello @Beau Bush
Please see this link and the answer from
Petterson Goncalves
https://community.atlassian.com/t5/Next-gen-questions/Can-t-Link-other-project-issues-to-next-gen-epic/qaq-p/937372
Hello @Nick Ivlev ! We understand that you’re using both Classic projects and Next-Gen projects for your organisation. Would you help us learn more about you and your use cases? A one-hour chat with you would be immensely helpful, and we’ll send you a $100 gift card as thanks. If you’re interested, please email me at echan@atlassian.com.
This is really bad. +1 to the need for this.
@Emily Chan, I can provide one use case where we have the exact same issue. We have a bunch of classic projects with lots of tasks and bugs. Due to reason that conversion from classic to next-gen will drop certain items from tasks, we cannot do conversion. We really would like to utilize next-gen project's roadmap feature. Epics that we want to maintain in next-gen project contains work from different teams that are using classic projects but this combination seems to be impossible.
It looks like you're new here. Sign in or register to get started.
