We're looking at migrating our project from next-gen to classic to access some of the old features that we need such as fix-versions. But I'd rather not have to migrate and then migrate back again if we change our minds about using the next-gen project.
So my question is, is it possible to, rather than migrate our data, duplicate our data into a classic project so that the next-gen project is untouched?
You might consider looking at this addon. While I do not have personal experience w/ it I have heard good things. I do not know if it support NG projects however. Deep Clone for Jira
Edit: Next-gen support added, see next post.
Thanks for mentioning our app Deep Clone for Jira @Jack Brickey
We're already supporting next-gen projects as much as possible and will release an update soon, allowing to cover more advanced use-cases like cloning an Epic along with all of its issues in a next-gen project.
I'll update this thread as soon as this has been released. Let me know if there are any issues using next-gen, we're keen to support next-gen as well as classic projects!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Update: We've just released next-gen compatibility! Let me know if anything doesn't work as expected.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.