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. 3. I'm on Firefox on Mac and Windows and the next-gen board is unusable. For a detailed overview on what gets migrated. Services. Next-Gen Project/Board: For Next-Gen, both board and backlog are visualised in the backlog screen. Mainly because the inability to share custom fields across projects and the link to Jira Align apparently works much better with Classic. 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. Export. Thank you for mentioning Deep Clone for Jira, @Ismael Jimoh . About Jira; Jira Credits; Log In. Jira classic to Next Gen Migration. Ask the community . So, the first. View a list of versions, their status (released, archived, unreleased) and the progress of that version via the releases page. There is an option to create a project with a shared configuration that copies the settings from a project to another, but it. I have not done this myself but the one thing I would convey is to plan your "epic" moves carefully as they don't migrate clean. Create . Next-Generation Jira Projects are an Atlassian Cloud feature designed to allow teams to collaborate on projects. When you integrate Aha! Roadmaps with a Jira team-managed project, Aha! Roadmaps will automatically detect the template type and create appropriate field. 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. 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. However there is no option to import the comments. :) I am going to. Hello, You should have read the guide for migrating next-gen to classic. Problem Definition Presently, anytime you convert a project between Next-gen and classic (or vice versa) the epic relationship between. Nilesh Patel Nov 20, 2018. There is a feature suggesting a migration tool for classic to next-gen: Migration tool from. Perform a cloud-to-cloud migration. Log In. 4. Answer accepted. Is there a way to avoid creating again all the stories, tickets and deadlines in this new project by migrating the datas from the 1st one?Hello! I will be migrating from Next Gen project to Classic and I have few custom fields made for my issues. Creating a Jira Next Gen project for each initiative, did not allow me to show all in one view, without going through unnecessary hoops. We use Classic projects for each of our development team, however the product team would love to use Next-Gen projects to track multi-project Epics. For example, I have two different Next Gen projects with project keys: PFW, PPIW. @Tarun Sapra thank you very much for the clarification. If you do choose to do this, keep in mind there would be an additional step because they are next gen projects, which do not exist on Jira Server. . The new Jira Service Desk Next-Gen project type comes as the simplified solution for easy to start and use for your help desks, without needing a Jira administrator. Classic projects are now named company-managed projects. Today, I’m thrilled to make some announcements in our endeavor to support extensibility for next-gen projects. The rule would be simple and would run when an Issue is transitioned to a Done (Green) Status. I want to migrate next gen to classic type project. Products Groups Learning . The columns on your board represent the status of these tasks. In that stage instance, I have created a Classic Project with the same fields as the NextGen Project and tested a few (3. Copied the home directory to the AWS EC2 instance and the rest is just making the connections as you said. It means that the site was already wiped. Sprints are associated to agile boards, not to projects. {"payload":{"allShortcutsEnabled":false,"fileTree":{"":{"items":[{"name":". Create a new template for another legal process by customizing the request types in Jira Service Desk project settings. Create . would be managed in a much more robust end simplified way, without losing the key functionality. Jira Work Management ; Compass ; Jira Align ; Confluence ; Trello ; Atlas Bitbucket ; See all. Jira Software Cloud; JSWCLOUD-17392 Team-managed software projects; JSWCLOUD-17263; Next-gen custom fields cannot be migrated to classic projects. . Hi Bill thanks for the reply. If you've already registered, sign in. Script to migrate a Jira Classic project to Next generation project - jira-classic-to-next-gen/README. However, you can move all issues from the classic project to the next-gen. Auto-suggest helps you quickly narrow down your search results by. Otherwise, register and sign in. Create . 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). 2. 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. We developed next-gen to allow teams to be more independent and autonomous, as many agile teams today have different ways of working within the company. 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. 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. Since the launch of Next-Gen last October of 2018, the name was found confusing. Either Scrum or Kanban will already be selected. Export worklog data from the source destination with the Tempo worklog servlet or by using the Jira Cloud Migration Assistant. ikshwaku Sep 07, 2021. If you've already registered, sign in. Log In. It might be a good idea to create a. Jira Issues . Jira next-generation projects. I'm trying to migrate data from next-gen to classic and when exported . 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. 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. In the end, we have given up on Next Gen and moved back to classic Jira. However there is a issue with migrating next-gen project types currently, and as Portfolio is not compatible with Next-Gen project types you should not have any next-gen projects tied to the Portfolio plans unless you are ok with the limitations covered in "Portfolio for Jira next-gen support" so the only limitation to look out for currently is. 5. 3 - Install the Configuration Manager add-on on your production server instance and follow the steps of the documentation below to. We have configured a Jira Next Gen project. Ask a question Get answers to your question from experts in the community. You must be a registered user to add a comment. Jira Software Cloud; JSWCLOUD-18112; Migrating Jira Next Gen Project to Classic needs to introduce drag and drop featureJira Cloud has introduced a new class of projects — next-gen projects. go to project settings. csv from next-gen and then import it to classic, i've faced with issue that epics doesn't include the tasks/stories. md file on the Repo. Regards,1 answer. When I try to create a new project I am given a choice whether to select Classic or Next-gen project. Access DOORS Requirements from Jira. 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. Click on the issue tab, the regular blue Create button appears at the top from which i create a new issue. Select whether you want to delete or retain the data when disabling Zephyr for Jira. And lastly, migrate data between classic and next. Log time and Time remaining from the Issue View. Now the user could see the values “Epic” (Classic), “Epics” (Next-gen), or “Rachel’s Super Special Epic” (Next-gen) when they query. 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. Second, we’ve built an intuitive new visual interface for next-gen project administrators to make. Our DBA made a copy of the on prem JIRA DB to an AWS DB instance (also same version of MS SQL DB). @Denis Rodrigues hi there! I see @Thiago Manini has pointed you to a solution. Otherwise, register and sign in. the only problem is that when you report, the. It would be my expectation that all comments are migrated from the ticket in Classic Jira to Next. 1 from Windows 2003 to Windows 2012. On the next screen, select Import your data, and select the file with your data backup. If you're upgrading both Jira Core and Software and Jira Service Desk during the migration process, upgrade Jira Core or Software only. Add the permission to Schedule Project for any roles/groups/users you want to manage and work the sprints. . I am using Jira board on a domain (eg. You can check the type of the project in the left sidebar: There’s a workaround if you still want to migrate data to the next-gen project. Click the Project filter, and select the project you want to migrate from. Thanks for reaching out and first, "Epics" are a native function in the next-gen projects, and additional details on working with epics in a next-gen project type can be found in: "Manage epics in next-gen projects". 3. is itCustom fields created in one Next-gen project cannot be carried over to other Next-gen projects. If you want,. existing project configurations from one instance to another via Project Snapshots. We’ve added a new card to the Jira Cloud Migration Assistant home screen that lets you migrate Jira users and. Is there a step by step on how to do that? Thanks, Gui. If you do choose to do this, keep in mind there would be an additional step because they are next gen projects, which do not exist on Jira Server. The migration tool makes migrating to Slack V2 Next Generation easy, and only needs to be completed once. It is pretty simple and with limited options of filtering (You can basically only filter by time). Click the Project filter button and choose the project you want to migrate from. 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. The. I dont seem to be able to create them in classic. 2 - Follow the guide below to migrate your next-gen project issues to a Classic project: Migrate between next-gen. migrating boards and all their data can be accomplished with Configuration Manager for Jira - an app which allows you to move, copy or merge. Now the problem with that as you've noticed comes with sub_task issues. 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. Upwards of 4 second lag when trying to just click and drag a card/ticket across columns. To go around this problem, you can either export all Standard Issue types separately and sub_task Issue type separately. Before I migrate our issues over to the new classic board I wanted to test it out before moving my team over. cancel. 3. Through filtering (project = "chris test" OR labels = onboarding AND project = "Chris test again" ORDER BY Rank ASC) I managed to show the issue in the backlog. When creating a project you choose between Classic or Next-Gen as the first thing. 1. 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 would suggest that Next Gen is simply badly named. Best you can do is create a new project and move the issues you want into it. How can I migrate from next-gen project to classic scrum project. I went into my Next-Gen project settings -> Features. Click on the magnifying glass, scroll to the bottom and in the Advanced search dropdown select projects. Select the issues you want to migrate and hit Next. Jira Core help; Keyboard Shortcuts; About Jira; Jira Credits; Log In. 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. Could anyone please confirm on it so. As a workaround, you may want to try to import the issues into a Classic project and then migrate them to a Next-Gen project as explained in: Migrate between next-gen and classic projects . md at master · maknahar/jira-classic-to-next-gen Next-gen projects and classic projects are technically quite different. Can I. If you are in a situation where you need to migrate projects with thousands of issues, it is physically not possible. Here's what I see as the important details. It seems like something that would save a lot of people discomfort/stress. Jira Software Cloud; JSWCLOUD-18112; Migrating Jira Next Gen Project to Classic needs to introduce drag and drop feature. Then I can create a new Scrum Board based on this filter, and those tickets. You can add it like. Turn on suggestions. Then I decided to start from scratch by creating a new project with the "Classic" type. In Jira server, we use both external directory. I am working with a few folks on moving their issues over from NextGen to Classic Projects. Based on our research, we know that this often starts as just. Jira Software Cloud; JSWCLOUD-18112; Migrating Jira Next Gen Project to Classic needs to introduce drag and drop feature. File Finder · maknahar/jira-classic-to-next-gen. md at master · maknahar/jira-classic-to-next-gen0:00 / 1:55 • Introduction How to Migrate Classic to Next-Gen Project in Jira Service Management? Help Desk Migration 379 subscribers Subscribe 0 Share 94. Jira also allows you to access your epics and issues directly from the roadmap, allowing the quick creation of epics and issues, and with many fun colors to style your epics. Since then, many of. Start a discussion Share a use case, discuss your favorite features, or get input from the communityClick on its name in the Backlog. But not able to move the custom field info to Classic. It would be my expectation that all comments are migrated from the ticket in Classic Jira to Next. When I try to create a new project I am given a choice whether to select Classic or Next-gen project. This might have negative performance effect on final Jira instance. Click NG and then Change template. @Charles Tan in order to start creating Classic projects please take the next steps: 1. 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. As a rule of thumb: keep in mind that next-gen projects were designed with simplicity of configuration in mind. 2. I am working with a few folks on moving their issues over from NextGen to Classic Projects. I want to migrate to classic because I'm deeply dissatisfied with the "next-gen" product. Ask a question Get answers to your question from experts in the community. Also the incompatibility is only at the project level, instance wide you can have a mix of both nex-gen and classic projects, with the classic projects usable by Portfolio with full functionality and next-gen with limited functionality. 4. Converting won't be possible, you'll have to migrate the project to a new one. 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. Both Scrum and Kanban templates of Next-gen projects have the exact same features and possibilities. 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. 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. Thats it. Classic projects provide more filters that you can configure within the board settings based on JQL filters. Next gen should really have this. A set of helper tools for importing issues from a classic Jira project into a next-gen project. Select Move Issues and hit Next. As a consequence. 4. Migrate Jira users and groups in advance ROLLING OUT. 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. Once you choose to add the issue to the board (drag-and-drop. If you want to change your Business project to a Software project, you can head to the Business project, select Project settings, and under Project type select. Nov 26, 2021. Default language in Classic can be set / changed anytime, but Next-gen has to be setup upon creation. There's an option to move issues from next-. If you have an existing Jira Software project, it probably isn't a Next-Gen project. Will our TM4J test cases associated with that project move with the rest of the records? If yes, will those test records/customized fields be impacted by this transfer?. There are better tools available than "next-gen" that are cheaper and faster than Jira. I tried to copy all issues to new next-gen projects, however, bulk change option allows me to copy upto 1000 issues at a time. There aren't really disadvantages to Classic projects at the moment. Reduce the risk of your Cloud migration project with our iterative method. Comment;The Next-Gen Project board looks amazing and alot less cluttered than the standard SCRUM/Agile Sprint board we are currently used to having on Jira. net) and we are buying another domain (eg. The same story with sub-tasks, they are imported as separate issues. Create a classic project and set up a workflow in that project. 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. Moving forward we have the following Feature. Apr 15, 2019. You must be a registered user to add a comment. Solved: Since you almost destroyed the tool with the new gen release, could you please provide a way to migrate our projects back to the previous. Have logged time show up in the Worklogs. 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. g. Indeed, with the Next-Gen projects and Epics being launched we can't use the Epic Link field to return issues that are linked to the Next-Gen epic as we can do for the classic projects. Much of the project comes preconfigured for either a scrum or kanban template. If you're looking at the Advanced searching mode, you need to select Basic. Our development teams are interested in hearing your feedback - the bottom of the sidebar in next-gen projects provides a quick way to send feedback right from Jira: Fill out the form and hit. Currently trying to utilize the Next-gen Jira, using the "Move" functionality to take a ticket from a Classic Jira project when attempting this it asked map field etc. 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. Ask the community . However, I don't have experience with Classic Software projects and am afraid of possible disadvantages I'm not seeing. Then, import your data to the classic project. Classic projects are now named company-managed projects. We have a complex predominantly Classic implementation of JIRA with multiple teams and projects. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Migrate from a next-gen and classic project explains the steps. There is a need to move a Next Gen project to Classic project. Answer accepted. This did not work. Click on the ellipsis at the top right. Jira does not support CSV import facility in next gen project. Add the "Time tracking" field to an Issue Type in Next-gen Project settings. Another way to migrate Jira is by doing a regular Site Import. 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. Next gen to classic migration . You can find instructions on this in the documentation. 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. I would like to move to a 'Next-Gen' board to take advantage of the additional functionality available - however, I don't want to lose sight of JIRA actions previously completed on the Classic board. Migrate Jira Next Gen Project from Kanban to ScrumI understand that we can do an export and import the issues into JIRA but we would lose history (when an issue was moved from a particular state to another, etc. To migrate Jira Service Management customer accounts, add Jira Service Management on the destination site to reduce the chances of migration failure. On the other hand, Team members having only assigned privileges can move the transitions in classic. choose the project you want from the selector screen. Your site contains next-gen projects. 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). . This is horrible and almost totally unusable for common tasks. What Jira refers to as "templates", are the default project configurations that you can select from when you create a project (eg: Scrum, Kanban, Bug Tracking, Project Management, next-gen, etc) and. Is there a process for moving those projects over to Classic? Are the steps outlined somewhere? Thank you! Comment Watch Like Dave Liao Migrating project from Next Gen to Classic anna. Migrate between next-gen and classic projects You must be a registered user to add a comment. You can create a workflow rule not to allow stories to move from one swimlane to the next. move all issues associated with an epic from NG to the classic project. Jira Software Cloud has new insights that brings metrics out of reports, and right to where teams plan and track their work. Hello @JP Tetrault & @Stuart Capel - London ,. I have been charged with setting up a project for a project for a fairly simple team migrating from Rally to Jira. Hope this information will help you. 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). I have recently set up a next gen project and cannot make use of JIRA portfolio or any reports - please can you advise if i can migrate back to the. Next-gen projects and classic projects are technically quite different. - Add the statuses of your next-gen issues to the columns of your board. The app is free to install and use. In JIRA next-gen projects, any team member can freely move transitions between the statuses. This gives the same options as in a classic project to upload a csv. More about roadmaps here. Add the "Time tracking" field to an Issue Type in Next-gen Project settings. 8 URL: We are trying to consolidate multiple JIRA instances into one instance at the enterprise level. 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. It would look something like this: 1. Hi, I miss the point of these features since they already exist in classic projects. 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. Issues that were in the active sprint in your classic project. 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. . 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. net. . Move them to the same project but the 'epic' type Jira Cloud here. Issue-key numbers should remain the same 3. This transition would be a change of type for an already existing project. Moving epics and issues manually from UI is cumbursome and time consuming. Thank you. When I move the issue form Next Gen to Classic it clears those fields. Log In. @Charles Tan in order to start creating Classic projects please take the next steps: 1. So you don't migrate "boards" but rather you migrate the issues from a Classic project to a Next-gen project. Teams break work down in order to help simplify complex tasks. Startup the script and follow the prompt to correct the Epic Links in your next-gen Projects. 3. 15. I need to add roadmaps to my Jira software project and link backlog user stories to epics from the roadmap. However, I don't have experience with Classic Software projects and am afraid of possible disadvantages I'm not seeing. Products Groups . The Fix Version is actually the built-in one. 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. Issues that were in the active sprint in your classic project. So, I would recommend - don't touch it. 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. 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. That way you could do an import of the epics first (or other higher hierarchies), then Stories, bugs. Data loss related to projects , comments or description related to the issues or on the state of the issues. We’ll keep you updated on their progress. While moving fields are getting moved but the values are missing for custom fileds. When using this option, you can migrate:. In the top-right corner, select Create project > Try a next-gen project. Next-gen projects are now named team-managed projects. 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. As I understand you want to migrate your application server but database will be the same. PLEASE allow JIRA next gen to have multiple boards for one project, ideally with the workflow: 1) board for PRODUCT manager to work on ideas, refine them, move further. Navigate to your next-gen Jira Software projec t. The next-generation convenience images in this section were built from the ground up with CI, efficiency, and determinism in mind. Search for jobs related to Jira migrate classic project to next gen or hire on the world's largest freelancing marketplace with 22m+ jobs. Migrating next-gen projects to classic 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. Products Groups . Requirements: 1. If you're looking at the Advanced searching mode, you need to select Basic. Jira Service Management. We plan to migrate on-prem Jira server to cloud. If the module that contains the object is not open, it is opened. thanks for this tip ! There is a plugin to move projects, but I don't know if it works in the cloud. I suspect that we are going to have to migrate the Next-gen projects to Classic templates. However, you can manually move your issues via bulk-move. 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. open a service desk project. Boards in next-gen projects allow you to. Hello, Is it possible to change/convert next-gen Jira project to classic? Products Groups Learning . This is going to be an important feature for allowing people to transition from Trello to Jira next-gen, as the current export-import process from Trello to Jira next-gen screws up labels. In the top-right corner, select more () > Bulk change all. My question, what is the easiest and cleanest way to migrat. Host and manage packages Security. Please check the below link for migration of projects in Jira cloud. 2. When I go through the steps to migrate my issues, the Confirmation screen shows a list of Removed Fields (see attachment). What I am wondering is if there. For example: Epic links and issue links: Any issue links in your classic project will not exist in your. I did have to update the base URL as it changed. It has a very clear overview on things to consider during that migration - both ways. Your Jira admin will need to create a new classic project. You must be a registered user to add a comment. Click the Jira home icon in the top left corner ( or ). Hello Atlassian Community! I am attempting a test migration of JIRA 6. Please help me to find reason to keep use JIRA and not move to another alternatives. 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. The requirement is to measure team and individual velocity across all projects. That being said, next. If you have been using Jira Cloud you will more than likely have noticed the new next-gen Projects that are now available. Ask the community . Since Deep Clone offers also some more advanced cloning options you might not have to update data after cloning. After that, you can move all your existing issues into the new project. If you change the filter associated with the board, that will affect the history of all the sprints associated with that board. . However, as a workaround for now. However there is no option to import the comments. Solved: Hi team, I have one Next -gen project in cloud. You can create a workflow rule not to allow stories to move from one swimlane to the next. Script to migrate a Jira Classic project to Next generation project - jira-classic-to-next-gen/README. I can't find export anyway, checked the issues, looking for this on a menu. It's free to sign up and bid on jobs. Atlassian Team. Search for jobs related to Migrate to jira next gen project or hire on the world's largest freelancing marketplace with 23m+ jobs. bulk move is so clunky and time consuming; we need a bulk-move from within next-gen that works like next-gen does; in a classic project, to change an issue type, I could do this from within the issue screen by simply choosing the new issue type. From the doc you've linked: Active sprints: Sprints in progress in your classic project won't move to your next-gen project. So what’s the. Project settings -> Issue types > (select the correct issue type) List of fields is now available and you can add. Since Deep Clone offers also some more advanced cloning options you might not have to update data after cloning. Note that, since the projects are different, some information might be lost during the process. So looking for options to clone the issues. The Project snapshot packages all the configuration data (you can also. Hi, @maknahar really handy project! It's shocking Atlassian themselves don't provide the bare minimum for this very common use case (no news here…) Are you. 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). Ask a question Get answers to your question from experts in the community. Jira Work Management ; CompassHi, I migrated issues and tasks from a Classic Business Project to a NextGen Project.