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

Rob October 19, 2020

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? 

1 answer

1 accepted

0 votes
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 19, 2020

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

basically, you would:

  1. create the NG project to receive the issues
  2. create a filter (JQL) to display all issue to be moved to the NG project
  3. Use Bulk edit
  4. select the Move option
Rob October 19, 2020

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? 

Like Jack Brickey likes this
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 19, 2020

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

Like Jack Brickey likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events