nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the best process for moving an old project into next gen?

Rob_fdqvsu

Team

We want to start moving some of our old projects to next gen...how do I do this and copy over the schemes, Workflow, request types and automation?

Accepted answers

Jack Brickey

there is this article - migrate-between-next-gen-and-classic-projects

basically, you would:

create the NG project to receive the issues
create a filter (JQL) to display all issue to be moved to the NG project
Use Bulk edit
select the Move option

All comments

Jack Brickey

there is this article - migrate-between-next-gen-and-classic-projects

basically, you would:

create the NG project to receive the issues
create a filter (JQL) to display all issue to be moved to the NG project
Use Bulk edit
select the Move option

Rob_fdqvsu

Thank you Jack..the ticket piece I get. It appears that in Next Gen you do not have the options to do the following:

to use WFs that have been created in Classic.
Use the automation rules you have created in classic without manually creating them
Use the request types you have setup in other projects without manually recreating them
Migrate SLA from the Classic project
Migrate calenders for SLAs from Classic Projects

So ...Next Gen is best for new simple projects that dont have many rules setup...if you have a complicated project it is better to leave put...correct?

Nic Brough -Adaptavist-

That is correct, Next-gen lacks a lot of the functions that Classic projects have.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud