Additionally, if you really need the ability to bulk move issues from backlog to a Next-gen Kanban board, I Suggest you two possible workarounds: 1 - Navigate to the project settings > Features > Turn-on Sprints for your project. Jira ; Jira Service Management Jira Align. I'm trying to migrate data from next-gen to classic and when exported . You may migrate to Slack V2 Next Generation by using the instructions below. Now, migrate all the tickets of the next-gen project to that classic project. 3. View More Comments. In the top-right corner, select more () > Bulk change all. Migrate between next-gen and classic projects. Using these new images will lead to faster image downloads when a. If you want to change the preselected template, click Change template, and select the appropriate template for your. If you have been using Jira Cloud you will more than likely have noticed the new next-gen Projects that are now available. . Portfolio for Jira next-gen support. Hi @Nikola Cosic, As far as I understand, this is currently only possible for classic Jira projects and not the next-gen ones. Mainly because the inability to share custom fields across projects and the link to Jira Align apparently works much better with Classic. I'm on Firefox on Mac and Windows and the next-gen board is unusable. In other words do the following: create new epics in new classic project; move your epic children one epic at a time and then using bulk edit assign the epic link for those issues to the new epic; rinse and repeat. Note: These templates are coming to classic projects soon. We set up a bunch of Jira projects as Next Gen and after a few sprints, I'm noticing some of the functionality is lacking for reporting and workflow. Script to migrate a Jira Classic project to Next generation project - File Finder · maknahar/jira-classic-to-next-gen. Script to migrate a Jira Classic project to Next generation project - jira-classic-to-next-gen/README. Issues that were in the active sprint in your classic project will be in the backlog of your next-gen project. 1 from Windows 2003 to Windows 2012. I tried to make a trial migration and it seems like these custom fields do not migrate to Classic project (I made the same fields in Classic to match the New Gen ones). Nearly a year ago we launched the next-gen template, where we reimagined parts of Jira Software Cloud’s core functionality. If you have been using Jira Cloud you will more than likely have noticed the new next-gen Projects that are now available. Next-Gen is still missing working with parallel sprints, etc. Bulk move issues into their new home. atlassian. migrate between next-gen and classic projects . Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Create . Select a destination project and issue type, and hit Next. Ask a question Get answers to your question from experts in the community. To create a backup for server, either: Bulk move important issues from next-gen projects into classic projects administered by schemes. I get a message that reads: Please note that 409 sub-tasks were removed from the selection and do not appear in the table below. Migrating project from Next Gen to Classic anna. So, the first. I believe the best way to transition your issues from a Next-gen to a Classic board keeping the custom fields would be by exporting and importing the next-gen issues to a Classic project using CSV format. Currently next-gen projects are not available on Jira server. Hey Ollie - I just encountered a situation with a customer where they were trying to integrate a Next Gen project via the Jira connector with Jira Align. The migration then follows three simple steps. Ask the community . . Configure your project and go Every team has a unique way of working. A Good Idea?” for that example and other implications. Ask a question Get answers to your question from experts in the community. We’ve added a new card to the Jira Cloud Migration Assistant home screen that lets you migrate Jira users and. Access DOORS Requirements from Jira. go to project settings. xml. Find and fix vulnerabilities Codespaces. Startup the script and follow the prompt to correct the Epic Links in your next-gen Projects. Thank you for mentioning Deep Clone for Jira, @Ismael Jimoh . Our new list view, available in both next-gen and classic project templates, helps you get an overview of all the issues in your project in a simple table that can be easily filtered, sorted, and exported. move all issues associated with an epic from NG to the classic project. Perform a cloud-to-cloud migration. Ask a question Get answers to your question from experts in the community. If you want,. Answer accepted. It's native. Things to keep in mind if you migrate from classic to next-gen. Meanwhile, I've tried multiple ways to migrate back to classic, yet the Description. Regards,1 answer. Then, delete your next-gen projects. Next-Gen is not supported by most of the third-party macro vendors. It's the official Atlassian Supported tool for these types of tasks. Your site contains next-gen projects. Next-Gen still does not have the required field option. Unfortunately, as Stuart noted above at this time, Advanced Roadmaps does not support next-gen projects, and will only work with the classic project types, so you will need to plan out which projects you want to see in the Advanced Roadmaps plans in advance and convert any Next-Gen. Hi All, I am migrating all the issues from next gen to classic in the step 3 what do I need to do if I want to retain the same epic names after the. Both Scrum and Kanban templates of Next-gen projects have the exact same features and possibilities. In your workflow, add a transition from "To Do" (or whatever status you end up having) to itself called "Migrate", and add a post function: copy the field value of "Story point estimate" to "Story points". Sprints are associated to agile boards, not to projects. Use bulk move for these issues to add Epic Link to Link them to the new epic. Ask the community . Agreed, this is completely absurd. Next-Generation Jira Projects are an Atlassian Cloud feature designed to allow teams to collaborate on projects. Dear All, Is it possible to migrate a next-gen project to classic project? Thanks a lot, Gianmarco. Doesn't anyone have any insight or comparison they can share?The Cumulative Flow Diagram is a new feature in JIRA Next-gen. If you select delete forever, the data will be completely removed and cannot be recovered. Migrating issues from Classic to Next-Gen. Is it possible to upgrade existing "classic projects" to. Is it possible to move a NextGen (kanban) project to a Classic Kanban, so that we can hook it up to the Portfolio Management?Several custom fields I have in Next Gen are not in classic. But information on the custom fields are lost during this transition. The function are still limited compared to classic project at the moment. 6 and higher and CCMA for version 5. Need to switch a project from Next Gen to a Classic Project type. We plan to migrate on-prem Jira server to cloud. I have administered Rally for 8 years, never used Jira, and want to understand real life pros/cons of using a Next-Gen or Classic Project. 2020 Reading time 5 mins Leading on from our popular first part – Get on track with roadmaps in Jira Software (Cloud), we wanted to go deeper on the subject and explain. Use Classic, it's more powerful, more mature, and clearly Jira won't move away from it, as it intended originally (judging from Next Gen name). Migrate between next-gen and classic projects . Another way to migrate Jira is by doing a regular Site Import. You are going to need to do some manual work. Exporting worklogs is only needed in cases where you have worklog attributes configured or if you have not migrated the worklogs to Jira Cloud with the Jira backup. 4. Next-gen projects are independent of other next-gen and classic projects, so the custom fields, workflows, permissions are not shared between them. Is there a way to migrate next-gen project to classic projects in bulk? Two years ago we started using Jira Cloud and I didn't really know what I was doing at the time and didn't really understand the difference between these two types. Moving forward we have the following Feature. There are better tools available than "next-gen" that are cheaper and faster than Jira. The specific steps would be: - Navigate to your classic board > Click on the three dots Icon > Board settings > Edit filter query. Through the ticket, they can access your site in order to help you with the migration. I migrated a project from Jira Next-Gen to Jira Classic. I want to migrate a NextGen project to Classic; however I see that NextGen is using a field called "Story Point Estimate" while classic is using "Story Points". Cloud-to-cloud migration helps you move users and Jira Software, Jira Work Management, and Jira Service Management projects from one cloud site to another. Upwards of 4 second lag when trying to just click and drag a card/ticket across columns. Moving epics and issues manually from UI is cumbursome and time consuming. In the end, we have given up on Next Gen and moved back to classic Jira. For more information about Next-gen projects. However, there was a lot of comparisons between Classic and next-gen as they both lived within Jira. The Project snapshot packages all the configuration data (you can also. atlassian. Best you can do is create a new project and move the issues you want into it. Have logged time show up in the Worklogs. As for features and themes, Themes are an additional function provided by the add-on app Jira Portfolio, and I. There is a feature suggesting a migration tool for classic to next-gen: Migration tool from. I am unable to provide any comparison. Ask the community . Jira Service Management. You will have to backup and restore attachments separately at filesystem level from the source host server to the target host server, either before or after import of XML data. cancel. Benefits of migrating to Jira Service Management from Halp; Requirements for using the Halp migration tool; Migrating from Halp to Jira Service Management. Classic projects are now named company-managed projects. Now featuring Dark Mode. 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. Create . Is there a way to move to classic without starting the project over? Regarding your second question, you can bulk move your tickets from next-gen to a classic project. So I'd like to move duplicate issues over to the new classic board and keep the next gen board with the issues for now. If there are any templates, macros, workflow settings that are valuable, make sure to. Create . Migrating from Halp to Jira Service Management. Additionally, this is the official page with all the details you need to know in order to migrate your issues between Next-gen and Classic Jira projects: - Migrate between next-gen and classic projects . I have reached an impasse when I am requested to select the project I am moving to as well as t he issue types (see image below). Move them to the same project but the 'epic' typeJira Cloud here. cancel. Hope this information will help you. You must be a registered user to add a comment. Ask the community . Converting won't be possible, you'll have to migrate the project to a new one. The new names of the projects are: Next-Gen Projects to Team-Managed ProjectsJCMA’s features resemble Configuration Manager, a popular Jira project migrating app: not only do you choose the projects to migrate, but also specific users and groups. Here's what I see as the important details. Appreciate any help!!! Track and manage all aspects of your team's work in real time from the convenience of your iOS or Android device with Jira Cloud mobile. If the link is an external link and the external link is a URL, the linked resource is. I am looking to move all of my stories from a next gen project back to a classic due to the lack of subtasks in the current next gen. Ask a question Get answers to your question from experts in the community. Our DBA made a copy of the on prem JIRA DB to an AWS DB instance (also same version of MS SQL DB). I am trying to determine the key features and functionality that would be lost using a Next Gen project type vs a Classic Project Type. Scrum vs. I'd suggest you to read the documentation before bulk move the tickets between projects: Migrate between next-gen and classic projects Additionally, we’ve renamed our project types (next-gen and classic) to make them clearer and more descriptive: Next-gen projects are now named team-managed projects. If you're upgrading both Jira Core and Software and Jira Service Desk during the migration process, upgrade Jira Core or Software only. I would recomend watching This Feature Request for updates. It will involve creating a new Classic project and bulk moving all of your issues into it. Select Move Issues and hit Next. Jira Work Management ; Compass ; Jira Align ; Confluence. Generally speaking, I would aim at building a new Jira, creating new schemes and configurations and then just importing issue/comments/whatever else you need. Currently our Instance has 300+ projects and lots of valuable data including 300K issues. However, I don't have experience with Classic Software projects and am afraid of possible disadvantages I'm not seeing. However, boards across multiple projects cannot be migrated automatically. If you need a customized workflow, Classic projects are where you want to be for now. It seems to work fine for me if I create a new Scrum board using a filter. Copied the home directory to the AWS EC2 instance and the rest is just making the connections as you said. Steven Paterson Nov 18, 2020. I would suggest that Next Gen is simply badly named. The main difference between the two is that Classic projects pull in pre-existing configurations from a global pool on your site (which are created and managed by your. Hi there, I’m Bree and I’m a Product Manager working on Jira Cloud. You can import your data to the classic project and then migrate data between classic and next-gen projects using the free solution from Jira Service Management. Your site contains next-gen projects. click on Create new classic project like in the picture below. Classic: To delete a field, you'll need to be a Jira Admin and then. Export a project from one JIRA instance and import it into another. I tried moving issues from a classical project to a next-gen project. For example: Epic links and issue links: Any issue links in your classic project will not exist in your. So data in those fields will be lost. Click on the magnifying glass, scroll to the bottom and in the Advanced search dropdown select projects. Teams break work down in order to help simplify complex tasks. It will take more time, but it will be nice and clean Jira with all the data you need. Problem Definition Presently, anytime you convert a project between Next-gen and classic (or vice versa) the epic relationship between. Create . I'm trying to migrate data from next-gen to classic and when exported . Perhaps it's the wise course, perhaps not. Today, I’m thrilled to make some announcements in our endeavor to support extensibility for next-gen projects. The functionality itself remains the same and continues to be ideal for independent teams who want to control their own working processes and practices in a self-contained space. Now, when you are moving epic(s) from a classic to a next-gen project (or vice versa), you would get a prompt asking if you would like to move the child issues along with the epic(s). 3. Now featuring Dark Mode. It would look something like this: 1. Create a new template for another legal process by customizing the request types in Jira Service Desk project settings. Can export the issues. When I try to create a new project I am given a choice whether to select Classic or Next-gen project. Either Scrum or Kanban will already be selected. To migrate Jira Service Management customer accounts, add Jira Service Management on the destination site to reduce the chances of migration failure. While Next-Gen doesn't have schemes, the Board column names act as the status names, so you would just need to choose the status as a part of the move operation. From your project’s sidebar, select Board. Is there a way to automatically pop. Classic projects are now named company-managed projects. Classic provides an option to setup a simplified status label for the customer's view, while Next-gen does not. My project was created as a classic software and I already have sprints completed, sprints ongoing + a full backlog in it. Log In. Use Classic, it's more powerful, more mature, and clearly Jira won't move away from it, as it intended originally (judging from Next Gen name). Is there a way to migrate a classic projects to Next-Gen project ? Products Groups . I can't find export anyway, checked the issues, looking for this on a menu. Create the filter and scrum board in the project in question and organize your cards into sprints. Indeed it's possible bulk clone up to 5000 issues between classic and next gen projects with our app. Jira Software; Questions; Migrating from Next-gen to Classic Software Projects; Migrating from Next-gen to Classic Software Projects . 4. Track and manage all aspects of your team's work in real time from the convenience of your iOS or Android device with Jira Cloud mobile. Hi Bryan, I can see that you are viewing the Agility Project (Next Gen Software Project) which is currently in beta stage at the moment. The solution here would be to use an Automation Rule (Global Rule for all Team-Managed projects or a Team level Rule) to auto-set the Resolution field when transitioning an issue for Jira Issues transitioned to a Done Status moving forward. It has a very clear overview on things to consider during that migration - both ways. While schemes. Benefits of migrating to Jira Service Management from Halp; Requirements for using the Halp migration tool; Migrating from Halp to Jira Service Management basics; Connect cloud site to Halp; Create a new service project for your Halp queue; Invite Halp agents to Jira Service Management Solved: My team would like to migrate from Next Gen back to Classic Jira. But if it is only the features covered in the KB above that you are missing and the portfolio application is accessible then converting the projects to classic would be the way to go, and details on converting a next-gen project to a classic project can be seen at the link below: Migrate between next-gen and classic projects The only way to convert next-gen project to a classic project is to create a classic project and move all issues from the next-gen project to the this classic project. One of the differences in comparison with the classic project type is that customer permissions should be managed only on the Customers tab, leaving the internal project. But they all seem to be disappeared. Search for issues containing a particularly fix version (or versions) via JQL. Currently Next-Gen Projects do not support the parent child relation ship that allows the higher initiative levels in Portfolio for Jira. If the reporting options for Next Gen projects are to remain so limited, how can we convert a Next Gen back to a "standard" aka, classic. Projects have opened in both Next-gen and Classic templates. Portfolio for Jira next-gen support. 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. 1. Next-Generation Jira Projects is an Atlassian Cloud feature designed to allow teams to collaborate on projects with an emphasis on being able to quickly tailor their board, fields, and other features without requiring a Jira Admin to make the changes. The. You are going to need to do some manual work. The Fix Version is actually the built-in one. Next gen to classic migration . notice the advance menu option. Jira Software Cloud; JSWCLOUD-17940; After migrating from Classic to Next-Gen it's not possible to bulk edit epic links. It's native. Ask a question Get answers to your question from experts in the community. If I select Classic I am given Kanban project by default, but if I click 'Change template' the list of different templates appears on the screen. Ask the community . On the other side… we now must migrate to Company-managed projects (former Classic) as your progress on Next-Gen roadmap did not move forward as much when it comes to our needs. View More Comments. The columns on your board represent the status of these tasks. After all the tickets were processed I wanted to check them in the new project. You must be a registered user to add a comment. Jira ; Jira Service Management. For future changes you can move issues between a nextgen and classic project, so whatever you decide, you can quite easily move all issues at a later stage. Feel free to watch on this blog to be notified of any changes: What's coming soon for next-gen projects in Jira Software Cloud. Practically, the only difference between one template and another are the features initially selected for each of them: In Scrum, your work is defined by Sprints and you need a time estimation to track and finish your work, while in Kanban you. Skip to content Toggle navigation. Jira Software Cloud has new insights that brings metrics out of reports, and right to where teams plan and track their work. I have a batch of tasks I want to make subtasks under another task. Hello, You should have read the guide for migrating next-gen to classic. Ask a question Get answers to your question from experts in the community. With classic Jira, we have set up triggers so that whenever a branch is created, the JIRA task goes into in progress, then when the PR is merged, it closes. Hello, We are trying to migrate data from to another JIRA version hosted in our AWS Ver 7. Scrum is a more prescriptive methodology that provides a structured framework for planning and executing projects. Then I can create a new Scrum Board based on this filter, and those tickets. Ask the community . If the module that contains the object is not open, it is opened. Hi @Harrison Wakeman , Assuming that you are migrating to cloud - if your boards are attached to a single project: yes. If you google it you will get to know more about bulk edit feature. 2. Script to migrate a Jira Classic project to Next generation project - jira-classic-to-next-gen/README. The ability to create Next-gen projects is enabled for all users by default. The fundamental concepts remain the same, but the UIs are different, so it's important to clarify that the screenshots in this article are from Jira Next-Gen, rather than classic Jira. I then select the destination Project and Status, and come to the screen where I tell it to Retain the values of all custom fields: However, in the next screen you can see that most of those fields are listed under both "Updated Fields" and "Removed Fields. . Currently, that tool causes several bugs: All issue types are forced to type 'Story' or 'Task' Story points are removedCan we convert JIRA Next-Gen to classic version because classic version can use Multiple Active Sprint. Very surprised by this oversight, and that a list of features that aren't included weren't added to the migration documentation. move all issues associated with an epic from NG to the classic project. Export. Hi @prashantgera,. I already tried to move the issues directly from next-gen to Classic-Jira project. I have been charged with setting up a project for a project for a fairly simple team migrating from Rally to Jira. Next-Gen is still missing working with parallel sprints, etc. open a service desk project. Hence it seems this field is only for sub-tasks. Create . Browse templates across the Jira products you own, with additional information to assist you in finding the template that best fits the way your team works. Create . 3. I want to migrate to classic because I'm deeply dissatisfied with the "next-gen" product. To change a story to a task etc I just click on the icon next. It's free to sign up and bid on jobs. About Jira; Jira Credits; Log In. Issue-key numbers should remain the same 3. It should be called Simplified Jira, or something that does NOT imply it's better/more up-to-date like the words "next gen" imply. And lastly, migrate data between classic and next. Project settings -> Issue types > (select the correct issue type) List of fields is now available and you can add. Would like to have a check whether will have any data loss related to user management or on access control after doing the migration. I went into my Next-Gen project settings -> Features. However, I don't have experience with Classic Software projects and am afraid of possible disadvantages I'm not seeing. 1 accepted. Only Jira admins can create. This means that every single team working in Jira Software Cloud will get access to a powerful basic roadmap. Ask a question Get answers to your question from experts in the community. There are a few things to note prior to migrating from Slack V1 and V2 to Slack V2 Next Generation:The sort order is controlled by the boards filter, which is a configurable option in classic Boards (as covered here) , but it is not configurable in the new next-gen boards, so at this time the issues Rank value is the only option you have for rearranging the issues in a next-gen project type. You would then choose the 'move' option and move them to the same project (the classic one you are migrating to) but to the 'epic' issue type. . - Back to your board > Project Settings > Columns. Avoid passing through a proxy when importing your data, especially if your Jira instance. I just checked on cloud instance, now the Priority is available. After that, you can move all your existing issues into the new project. Hi Team, I have tried to move the Next Gen Issues to Classic project. 4. Project admins of a next-gen project can now access email notifications control via the Project Settings. Unfortunately, as Stuart noted above at this time, Advanced Roadmaps does not support next-gen projects, and will only work with the classic project types, so you will need to plan out which projects you want to see in the Advanced Roadmaps plans in advance and convert any Next-Gen projects to classic projects to make this happen, details on. If. For example, I have a rule that says that a story cannot move from To Do -> In Development when the "Requesting Customer". Classic projects are now named company-managed projects. 2. This might have negative performance effect on final Jira instance. Ask the community . Otherwise, register and sign in. In JIRA next-gen projects, any team member can freely move transitions between the statuses. Kanban is a more flexible. You will need to set them up again in your cloud instance after migrating your projects. Thanks for the answer, I was hoping I won't have to create the 100+ epics into the old generation project but I will do this. The workaround for this in `next-gen projects` is to use the `Move` option to move the card to the same project but with a different issue type. Issues that were in the active sprint in your classic project. Click the Project filter, and select the project you want to migrate from. When I try to create a new project I am given a choice whether to select Classic or Next-gen project. Check out the following Developer Blog on this topic that goes into more detail on this: Jira Cloud next-gen projects and the effects on the REST API. Log time and Time remaining from the Issue View. Since Deep Clone offers also some more advanced cloning options you might not have to update data after cloning. Currently, there is no option to clone or duplicate a next-gen project. We are planning to migrate JIRA cloud to datacenter application. It means that the site was already wiped. If I select Classic I am given Kanban project by default, but if I click 'Change template' the list of different templates appears on the screen. . Currently, there is no way to convert next-gen to classic projects. If I understood correctly, the goal of Next Gen was to simplify JIRA, namely: how workflows, custom fields, custom screens, permissions, etc. Oct 09, 2018. open a service desk project. I believe the best way to transition your issues from a Next-gen to a Classic board keeping the custom fields would be by exporting and importing the next-gen issues to a Classic project using CSV format. Click on the ellipsis at the top right. I have created another (stage) free instance and restored the original to that so I so not impact the users work in any way during testing. I have created another (stage) free instance and restored the original to that so I so not impact the users work in any way during testing. If it's a Next-Gen project, it will have the Features option: If you don't see Features in Project. I'm experiencing the same issues. This document should help you out - migrate-from-an-next-gen-project-to-a-classic-project Recently started working for a Fintech where there a number of open projects. As Atlassian recently announced, they made the app custom fields available to instances enrolled in the Jira Cloud Vendor First Release program on June 24th. net) and we are buying another domain (eg. Ask the community . This change impacts all current and newly created next-gen projects. 1 accepted. - Add your Next-gen issues to be returned in the board filter. It seems like something that would save a lot of people discomfort/stress. Here's a few things to consider when you migrate from a classic software project to a next-gen software project: Active sprints: Sprints in progress in your classic project won't move to your next-gen project. @Charles Tan in order to start creating Classic projects please take the next steps: 1. I hope that helps!-JimmyThe closest you can get is to create a new project of the right type and move the issues from the old project into the new one. Next-gen projects and classic projects are technically quite different. Can I. 2. We have a feature request suggesting the implementation of quick filters on next-gen: Ability to create quick filters in Next-gen projectMigrating Jira board from existing domain to another domain. They come with a re-imagined model for creating, editing and representing project settings. Products Interests Groups . 1. Now, migrate all the tickets of the next-gen project to that classic project. I've created a project with the "New generation" tools but the functionnalities finally do not fit my actual needs. For each task, it takes me about 5 clicks, including finding the right parent task from a list of poorly numbered tasks, from the roadmap view, and then I can't see the subtasks on the roadmap, so I have to go to the advanced roadmap to see. 1 - Use a third-party app to facilitate the process, like the Freshworks App. Using TM4J for our test cases in Jira Next Gen and Classic Projects. Click on the 'issue types' option in the project settings' menu. Create . I want to migrate to classic because I'm deeply dissatisfied with the "next-gen" product. atlassian. 2) board for DESIGN, ideally would be triggered by a workflow: once task has "ready for design" status, it would jump into "todo" on designer's board. It might be a good idea to create a. This application is meant to be used in conjunction with the JIRA's built-in CSV issue importer. Next-Generation Jira Projects is an Atlassian Cloud feature designed to allow teams to collaborate on projects with an emphasis on being able to quickly tailor their board, fields, and other features without requiring a Jira Admin to make the changes. Mar 01, 2021 Hi Sophie, welcome to the Community! So you don't migrate "boards" but rather you migrate the issues from a Classic project to a Next-gen project. On the Select destination projects and issue types screen, select where issues from your old project will go. This Project has 5000+ Issues and I need to migrate it to our Production instance. Next-gen projects and classic projects are technically quite different, so a few things can break when you migrate from a classic software project to a next-gen software project. Alexey Matveev Rising StarMigrating Jira projects from Next-Gen to Classic Giovanny MACARTHUR Apr 07, 2021 Team, We are looking to move from Next-Gen to Jira Classic but have a. - Add the statuses of your next-gen issues to the columns of your board. To create a backup for server, either: Bulk move important issues from next-gen projects into classic projects administered by schemes. @Charles Tan in order to start creating Classic projects please take the next steps: 1. Much of the project comes preconfigured for either a scrum or kanban template. Alex Nov 25, 2020. Now the problem with that as you've noticed comes with sub_task issues. Note though that if your cloud instance has any Next-gen projects, you will need to migrate all project data to non next-gen projects and delete them before being able to create a backup for server, as Jira Server does not allow next. Navigate to the Next-gen Configuration page: Project settings → Apps → Nex-gen Configuration. I want to migrate next gen to classic type project. However, as a workaround for now. Click on Move. Overall it sounds like there could have been an issue installing. Unfortunately, You are correct to say that the custom fields of Classic Projects are not applied for Next-Gen Projects. 2.