We are faced with the problem of linking the task of the classic project to Epic in the nex-gen project.
Project A - classic
Project 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 ! 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 email@example.com.
@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.
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