The ability to make arbitrary API requests to your JIRA instance where the headers will be properly set with a security context/session for the workflow agent. Click NG and then Change template. I am also on jira cloud. But I cannot find a way to get "Resolution" to appear at all in my next-gen software projects. Hi @Michael Galper To allow users to create Classic projects you might have to add them to Administer Jira global permissions (which is a dangerous thing to do). Select Projects. in the end I just gave up on. Rising Star. An explicit Action type to move an issue from the Board to the Backlog or vice-versa. Ask the community . . Next-gen and classic are now team-managed. Give your. I have created the custom fields same as in Next Gen projects. with next Gen. Is there a way to go back to classic. Since Deep Clone offers also some more advanced cloning options you might not have to update data after cloning. Hence, company-managed projects have. Or is you still have your projects labelled as so, be sure that such labels are going away. Things to keep in mind if you migrate from classic to next-gen. Or, if you would like you can "move" all the issues inside "next gen" project to the Kanban one (you can search for all issues and move all results at once) Thank you @Jack Brickey for the link. If you have a Business project, it could be that you went to create a project at some point, and selected a non-software project template (eg: Project management, Lead tracking, etc). If it's Next-Gen, whilst you can disable Next-Gen projects (which the Roadmap function is part of), you can't stop paying for it specifically - Next-Gen and Classic. You can easily distinguish a next-gen project from a classic project by the Roadmap feature. Bulk transition the stories with the transition you created in step 2. The Roadmaps feature is currently only available in Next-Gen projects. Every project requires planning. 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. Could you please provide us this information with a screenshot of your Issue view?Search for jobs related to Change next gen project to classic jira or hire on the world's largest freelancing marketplace with 22m+ jobs. The option to move can be found in different places, depending on your JIRA platform (Cloud or Server), the kind of project (Classic or Next-gen) and the view you are currently using. The permission to create these projects is granted globally to the group of Jira users via the "Create team-managed projects" global permission. Where did the issues/tasks go?Both Scrum and Kanban templates of Next-gen projects have the exact same features and possibilities. 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. 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. 4. If I understood correctly, the goal of Next Gen was to simplify JIRA, namely: how workflows, custom fields, custom screens, permissions, etc. Like • anna. 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. Since March 2021 you might have noticed that there is no longer a “next-gen” or “classic” project in Jira (cloud). choose the project you want from the selector screen. Jira; Questions; Can you convert a legacy project into a next gen project? Can you convert a legacy project into a next gen project?. If you are just trying to make the old gen project private, all you need to do is change the browse project permission in the permission scheme to the correct user, group or project role. In Choose project type > click Select team-managed. Example: Acme Inc are about to kick off a project with the goal of increasing checkout conversion for their online shopping cart. I am familiar with the search and bulk edit feature in the classic on the issues page, but I do not see the tools menu of issues page in the next gen. It's free to sign up and bid on jobs. You still cant change the project type but the. Business means "Jira Work Management". The swimlane are even same for both projects. Fix version, can be tagged to release. Issue types that I am going to import depend on the project configuration where you want to import tasks. Search for jobs related to Jira next gen project vs classic or hire on the world's largest freelancing marketplace with 22m+ jobs. To restrict your Next-Gen projects to only specific users, you must follow the steps below: - Navigate to your next-gen projects > Details > In the Access field, select private: - In the tab people, define which users should be able to access the project, selecting the role you want for them. 2. What is changing? After our 2018 launch of next-gen in Jira Cloud, we heard consistent feedback from customers that its name, next-gen, was confusing. I want to create roadmap for multiple classic projects that are in a single board . "The ability to wrap one's head around effective classic project configuration is what often separates a Jira veteran from the casual user. It enables teams to start clean, with a simple un-opinionated way of wo. That being said, you can simply create a query to display Epics of the project you want. 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 actually found a work around to print the cards from next gen project. The Next-Gen projects were created to give an option for those teams which are looking for a simpler solution than the conventional JIRA projects. Now, to fix the link of issues. Having Company Managed (previously known as Classic) projects and Team Managed (previously known as Next Gen) projects in one Jira instance is possible only when you are using Jira Cloud. Also, when you refer to Roadmap do you mean the roadmap in Next-Gen or a separate app? If it's a separate app, your Site Admin can manage apps from the administrator console. Select Projects. 3. @Brant Schroeder I want to clarify my question above. I want to assign them as ordinary tasks into a next-gen project. Creating a Jira Classic Project in 2022. Next, walk through the Bulk Operation wizard to move your issues into your new project: Select the issues you want to migrate and hit Next. 4. For example, issues in the In. Hi, I'm a little confused on how to add a subtask to an issue in a Next-Gen project. Now they will always be assigned the issue once it's created. I should be able to flatten out sub-tasks into tasks, during such an edit. Let me know if you have any concerns. @MarekSpalek Yes, we plan on adding support for users to manage Versions/Releases in the next-gen project. 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. Ask a question Get answers to your question from experts in the community. Next-gen projects and classic projects are technically quite different. But a workflow is one of the more difficult aspects of setting up a project, get it wrong and you can create chaos. Move your existing issues into your new project. 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. Projects have opened in both Next-gen and Classic templates. Create . How do I change the project to classic? I can't find the option to do that. 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. 2. We have some feature requests suggesting. Create a team managed project with an Epic; Assign some issues to that Epic; Using the bulk operations, move multiple issues in that project including the epic to a Company managed project; Expected Results. Hi @Michael Sueoka , To move your tickets from a Scrum board to a Kanban board, you could open individual ticket and then click on move from the dropdown which appears on clicking triple dot (. Create . Export. Either Scrum or Kanban will already be selected. Cheers, Jack. Jira Work Management ; CompassPortfolio for Jira next-gen support ; 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. I've tried using. Advanced and flexible configuration, which can be shared across projects. In next-gen projects you can go to "Sprint Burndown Chart" and there you'll be able to see "Scope Change Logs", "Incomplete Issues" and "Completed Issues" just after the graph. Learn more about the available templates and select a template. Choose between a company-managed project or Try a team-managed project. 1 answer. Otherwise, register and sign in. So you don't migrate "boards" but rather you migrate the issues from a Classic project to a Next-gen project. A ha. ThanksCari pekerjaan yang berkaitan dengan Jira convert next gen project to classic atau merekrut di pasar freelancing terbesar di dunia dengan 22j+ pekerjaan. Turn on suggestions. click on Create new classic project like in the picture below. If you're looking to use the Release feature, you can bulk move the issues to a classic board. Is there a process for moving those projects over. Ask a question Get answers to your question from experts in the community. Subtasks are now available in next-gen projects, and moving subtasks issues from classic to next-gen projects is also now possible. With team-managed service projects, your teams can manage their own work and process, without having to reach out to a Jira admin. The closest you will be able to come is to create an Automation For Jira rule to automatically create the tasks when the new project is created. There are four types of possible migrations: 1. The tabs concept in classic is so useful. Classic projects provide more filters that you can configure within the board settings based on JQL filters. Dec 07, 2018. Related to restrict this client to only see this project, it will only happen if the other next-gen projects are also private. And search that we can not convert next-gen project to classic. Looking ahead into 2020, roadmaps will increasingly become part of Jira Software’s core promise to help teams plan, track, release, and report on their work. ”. Having tried the next-gen templates out recently they are lacking some of the most important features – issue schemes, workflow association etc. Log time and Time remaining from the Issue View. enter filter in the search bar, e. Unfortunately, you can not link issues that are not from a next-gen project with Epics from a next-gen project because this kind of Epics does not have an Epic-name. greenhopper. Select the issues you want to migrate and hit Next. We’d like to let you know about some changes we making to our existing classic and next-gen project type labels. You can't copy Next-gen projects from a "template" like you can with Classic Software or Jira Service Desk projects. S: If you are not using this way, please let us know how you are searching for issues. But, there is workaround-. Setup and maintained by Jira admins,. Issue-key should remain the same. Most data will not transfer between projects and will not be recreated see. You can add your next-gen project to any of the categories (pre-defined by your Jira admin) from the Details page in Project settings. 3. I want to enable the testers to create next-gen projects. Then, on the top right, select. Either Scrum or Kanban will already be selected. You must be a registered user to add a comment. I can only change the name of the project there, the picture and switch to another project owner if there would be other people in my organization. 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. Portfolio for Jira next-gen support. Search for issues containing a particularly fix version (or versions) via JQL. Please, refer to the following page:. If you want to 'convert' your classics boards into next-gen boards, the best option for you is to bulk-move your issues. If you go into your system and to the "back-up" management section it will actually list all of your next-gen projects. When you create a next-gen project you have the option to choose if it will be Open, Limited or Private. In this type of project, the issue types are natively implemented. If you are using a server the server platform and you wouldn’t be able to sit. Step 2: Project plan. . Comparison between JIRA Next Gen and Classic Project type. If you have an existing Jira Software project, it probably isn't a Next-Gen project. whilst I can get subtasks for tasks,stories etc to link through the import, it is not possible yet to link the story to an epic (this is on the roadmap for 2020). md file on the Repo. We reinvented the Sprint Burndown. And search that we can not convert next-gen project to classic. Jira Work Management ;Hi, I miss the point of these features since they already exist in classic projects. Roadmap designing is friendly. Open subtask, there is "Move" option in three dots submenu. Jira Software Cloud JSWCLOUD-17392 Team-managed software projects JSWCLOUD-18643 When migrating between next-gen and classic projects Epic links info is lost and. Discover IT service management (ITSM) Learn about ITSM and the strategic approach to designing, delivering, managing, and improving the way businesses use IT. The other EasyAgile user stories only seems to work with next/gen. You can also customize this field. For this, we’re excited to share we’re bringing the next-gen roadmap directly into classic projects. Hello, Is it possible to change/convert next-gen Jira project to classic? Hi there, I’m Bree and I’m a Product Manager working on Jira Cloud. Other users can only create Next Gen projects. pyxis. Without apps I don't believe you can clone directly from a Classic to Next-Gen project, but you can definitely move an issue from Classic to Next-Gen. I desperately need to migrate a Next-Gen board back to the Classic, usable view. Ask the community . These are some of the third-party options available to achieve this functionality: Easy Agile Roadmaps for Jira. There is an option to create a project with a shared configuration that copies the settings from a project to another, but it. Click on the ellipsis at the top right. . 2. 4. If it's Next-Gen, whilst you can disable Next-Gen projects (which the Roadmap function is part of), you can't stop paying for it specifically - Next-Gen and. you board is now created. It was a ToDo item. Click the issue and click Move. That being said, if you. Related to Projects, comments or description : thanks for the confirmation. TMP = next-gen. On a classic project you would have to create a new sub-task type of bug (maybe call it bug subtask) and then add it to the issue type scheme associated with the project. The prior class of projects was called classic, so this is what we all get used to. Select the issues you want to migrate and hit Next. Tarun Sapra. So being able to organize the plethora of fields in a ticket is essential. Next-gen admins will notice that they can not change the workflows in their projects, so if you are looking for something other than the three-step To Do, In Progress, Done workflow, you will have to consider a classic project. Products Groups Learning. pyxis. Go to the project "Learn Tiger Style Kung Fu" with the key "FUJOWPAI" 2. Is is possible to fi. However, board settings are available within the classic project. I’m pleased to announce that keyboard shortcuts have arrived for next-gen projects! Keyboard shortcuts are a table-stakes feature of a modern cloud SaaS product in 2020. We still don't know when it will be implemented for Business projects. you can't "migrate" precisely in that there is no 'button' to migrate. For more details about the differences between Next-gen and Classic projects, you can check the documentation below: - Core concepts behind Jira Cloud next-gen projects and ongoing changes to our existing APIs. If I choose Next-Gen, I get only Kanban or Scrum as choices. However, you can move all issues from the classic project to the next-gen. If you've already registered, sign in. It was a Next-gen template. @Loïc D_HALLUIN don't hesitate to contact our support if you have questions or feedback about our Marketplace app. Search for jobs related to Migrate to jira next gen project or hire on the world's largest freelancing marketplace with 23m+ jobs. I agree with you that it can cause some confusion. Ask the community . If you are talking about the Dashboards that are created from the Dashboards menu option in the menu bar at the top of the screen. Start a discussion Share a use case, discuss your favorite features, or get input from the community Portfolio for Jira next-gen support ; 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. Next-gen projects are independent of other next-gen and classic projects, so the custom fields, workflows, permissions are not shared between them. For more information about Next-gen projects. If you're using Jira next-gen projects, support for JQL behaves differently compared to classic Jira projects. Choose project type: Company-managed. I want to assign them as ordinary tasks into a next-gen project. Can you please give the detailed differentiation in between these two types. Unfortunately, You are correct to say that the custom fields of Classic Projects are not applied for Next-Gen Projects. Project Settings -> Advanced -> "Create new classic project" 1 accepted. If you choose private only people added to the project will be able to see and access the project. You must be a registered user to add a comment. Describe users and roles in a project (standard users, project administrators, next-gen project access). 1. @Clifford Duke In the future we will offer a cross-project view. I created next-gen project which is easier to manage but there are lot of things not present in it like most of the reports, selection of timezone, components and release etc. Select the requests you want to migrate > Next. With that said, if you need more fields it will be necessary to use Classic projects. Fix version, can be tagged to release. You can use Bulk Move. Navigate to the Next-gen Configuration page: Project settings → Apps → Nex-gen Configuration. while @Nic Brough -Adaptavist- is correct, there is no way to. If you use Jira Software Cloud, check out this article to learn about creating a next-gen Scrum or Kanban project. Steve Perry Jan 14, 2019. It was created to be more simple since we spent more time when creating Kanban and Scrum projects, so it will not be possible to convert the project to Business and Service Desk because these templates are not available for these products. I see there is a text displayed: " You don't have permission to create a classic project. Products Groups . Next-gen projects provide a streamlined experience, are easier to use, and quicker to set up than classic projects. Select Move Issues and hit Next. Is it possible to update Insight assets from a next-gen service project? According to the Insight documentation, you can do this in a classic project through a workflow transition post-function. Project Administrator: A Project administrator, as we mentioned before, can change project settings and roles, assign members to groups, and enable or disable specific features. Essentially in a team-managed project, the team using that project can configure their own specific issue types, fields and workflows whereas a Company managed project configuration is determined by a jira administrator allowing projects to share configuration. Search for jobs related to Jira convert next gen project to classic or hire on the world's largest freelancing marketplace with 22m+ jobs. I'm attempting to bulk edit issues from a classic project. Ta da. So, click on Create Project Then click on Jira Software in the bottom left Select Kanban or. Now featuring Dark Mode. Let me know if you. Create a classic project, with similar issues available in your next-gen project (if you want a smooth transition) Head over to Jira Software -> Settings -> Backup manager (listed under headline "IMPORT AND EXPORT") Under "Back up for server" there should be a list of projects and an action for your project available to "Move issues", click. Python > 3. With next-gen projects they are not compatible with a migration to the server platform, and you would first want to look int converting the projects from next-gen to a classic project, then plan the move to the new platform. 5. Think Trello, for software teams. On the Select destination projects and issue types screen, select where issues from your old project will go. Classic projects are now named company-managed projects. It seems to work fine for me if I create a new Scrum board using a filter. fill in info and choose you profile (very bottom of list) for Location. The third one is configured by project team members. open a service desk project. Give the role a name, an appropriate description, and the permissions you would like to associated to that role. If you have any other questions regarding this matter, please let us know. If its just a situation of which template you used for a JSD project, thats no big deal. The following is a visual example of this hierarchy. How to do it. 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. Click the issue and click 'Task' in the top left in an attempt to convert the Task to a Subtask. Requirements: 1. Search for jobs related to Jira next gen project vs classic or hire on the world's largest freelancing marketplace with 22m+ jobs. Hi @Joe G, Next-Gen projects don't use custom fields globally across projects like classic projects, that is why you don't see a "field scheme. To create a new project (see Figure 1 for field details): Go to Projects menu on Projects page in Jira . When using Jira Service Desk next-gen projects, the limit of fields in a project is 50 and it's not possible to increase it. Products Groups . Is this really still not possible? This is the only reason why we can't migrate at the moment. However, even if i change the key of the old project, i can't apply the old key to the new project. The roles created by Jira it's not possible to edit and by default, the Member role doesn't have permission to manage watchers, but you can create a new one. Click Select a company managed template. An update on next-gen projects customer feedback – March 2021. If you’re using Azure DevOps Server, choose that instead. However, as a workaround for now. Next-gen is independent of Classic projects. That being said, if. 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. When creating a project, I no longer see a selection for Classic vs NextGen. Create . It only allows issue to be changed to Epic or Story even though Subtask is clearly a defined issue type for our project. Several custom fields I have in Next Gen are not in classic. Change destination type to "Story". What I recommend as a workaround is to add a category called Next-Gen and add it to each NG project. Only JIRA administrators can create classic projects, but any user can create next-gen 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). Hi Team, I have tried to move the Next Gen Issues to Classic project. Took me ages, but finally figured how to add a default assignee for Next Gen Issues. If you have a Business project, it could be that you went to create a project at some point, and selected a non-software project template (eg: Project management, Lead tracking, etc). I know a LOT of people have had this issue, asked. I plan to learn more (and will watch this thread), but I don't have the time for that rabbit hole right now. Also, right in the beginning of the page you can filter through the sprints, even the past ones. Next gen projects are not a good way to work in if you need to move issues between projects. Both of these options will move your page into the Blog section of the space where the page was created. I am trying to bulk move issues from my classic project to a next-gen project. Products Groups Learning . Or, delete all next-gen projects and their issues outright. to Convert to blog. Jira Cloud has introduced a new class of projects — next-gen projects. Once you have cloned the epic, go to the cloned one and again click the ellipsis and this time select Move and then move it to your next-gen project. . 2 - Map them in the Issue Types Mapping page. click on Create board. If you accidentally made a Software project instead of a Service Desk Project, you would need to create a new project. Importing issues from CSV to next-gen projects is possible as long as you don't map any custom field in the Next-Gen project. Custom project permissions appear under the 'App permissions' tab. To copy an epic to a next-gen project (also works for copying to another classic project) go to the epic and click the ellipsis button up in the right-hand corner and select Clone. Create a kanban board in the classic project. Click the Jira home icon in the top left corner ( or ). We are trying to author a requirements document and create the epics and user stories as part of that authoring. IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. The columns on your board represent the status of these tasks. How can I convert it to classical type Jira Project ? 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. When I create a new project, I can only choose from the following next-gen templates. Click the issue and click 'Task' in the top left in an attempt to convert the Task to a Subtask. Subtasks are now available in next-gen projects, and moving subtasks issues from classic to next-gen projects is also now possible. It allows you to customize the hierarchy between issue. Please review above bug ticket for details. It's free to sign up and bid on jobs. When I go through the steps to migrate my issues, the Confirmation screen shows a list of Removed Fields (see attachment). Create and assign an issue to a particular fix version. However, I don't have experience with Classic Software projects and am afraid of possible disadvantages I'm not seeing. Answer accepted. If. Search for jobs related to Change next gen project to classic jira or hire on the world's largest freelancing marketplace with 23m+ jobs. Additionally to that options, I suggest you to vote and watch the suggestion below to increase its priority and also receive notifications about any updates: Enable Roadmap. 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. You can however link the bug to the issue that you would like to associate it with. In issue type,can easily drag and drop the JIRA fields. Start a discussion Share a use case, discuss your favorite features, or get input from the community. Next-gen admins will notice that they can not change the workflows in their projects, so if you are looking for something other than the three-step To Do, In Progress, Done workflow, you will have to consider a classic project. It's free to sign up and bid on jobs. It's worth noting there are certain features in Jira that. We have several departments tracking tickets and each dept cares about certain things (custom fields). We have a classic project with a lot of issues with subtasks. Jira Work Management ;Here's a few things to consider when you migrate from a next-gen software project to a classic software project: Board statuses: If you customized your next-gen board, you'll need to set up the same statuses in your classic project's workflow. click on advanced search. Next-gen only works for the project type "Software". Click use template. Issue-key numbers should remain the same 3. Hi I used JIRA Service Desk cloud for free planning, the question is my JIRA Service Desk template for Next Gen is empty. Complete control over workflows, issue types, custom fields, permissions, and just about anything else you can think of. Download the free Jira Cloud for Mac app for a snappier, native Jira experience. Start your next project in the Jira template library. I hope that helps!. please attach the screenshot also :-) Thanks, PramodhOpen ‘Issue Types’ in the project settings of the next-gen project and select the Issue Type for which you would like to configure restrictions for. 3. While I wish that there was something in the Projects view page by default there is not. Hello! It sounds like you have a special interest in releases. the image below is in Next-Gen project setting. I have another site that started on 2020, I have next get project for service desk. 2. > Bulk change all X issues. Click on "Create Role". Click on its name in the Backlog. In the project view click on Create project. I did not find a way to create a next-gen project. Click the Project filter button and choose the project you want to migrate from. Then, in the top-right corner, select more (three-dot sign) and Bulk change all. This is a pretty broken aspect of next-gen projects. A quick way to tell is by looking at the left sidebar on the Project Settings section. We really would like to utilize next-gen project's roadmap feature. In fact, the link works in the same way in both templates, so that should not give you any errors with the Classic to next-gen migration. We are using a next gen project for bugs. There is a feature suggesting a migration tool for classic to next-gen: Migration tool from classic to next-gen project; For more details about what data is lost when migrating from one project type to another, please check the documentation below: Migrate between next-gen and classic projectsHi Phil, welcome to the Community. Please kindly assist in. Classic project: 1. Would you help us learn more about you and your use cases? A one-hour chat with you would be immensely helpful, and we’ll send you a $100 gift card as thanks. And also can not create classic new one :) please help and lead me. Daniel Tomberlin Oct 25, 2019. This requires Admin level permissions within the cloud environment. If you need that capability, you should create a Classic project instead of a Next-gen project. Here is the backlog. Due to reason that conversion from classic to next-gen will drop certain items from tasks, we cannot do conversion. Jira Cloud for Mac is ultra-fast. Next-gen and classic are now team-managed and company-managed. Or, if you would like you can "move" all the issues inside "next gen" project to the Kanban one (you can search for all issues and move all results at once) Thank you @Jack Brickey for the link. Bulk move the stories from NextGen to classic. there's no way to swap a project between Classic and Next-gen. In fact, Next-gen projects were created to provide simple functionalities for teams which do not need the complexity of JIRA software as Contexts for Custom fields, Field Configuration Schemes, etc. Some of the instructions were a little out of date but overall it was very helpful in getting me to the right place. Thanks!I don't have the option to create a classic project, I can only choose next-gen project. I started with 83 issues and now on the new board, I have 38. Jira Software Cloud; JSWCLOUD-17392 Team-managed software projects; JSWCLOUD-18643; When migrating between next-gen and classic projects Epic links info is lost and instead conversion should automatically maintain this data link between project typesHello! I will be migrating from Next Gen project to Classic and I have few custom fields made for my issues. JSD Next-gen projects are more simple than Classic ones, so there are features that are currently not available. Is it possible to convert a legacy project to a next gen project? Answer. So what’s. I haven't used Automation with Next-Gen projects yet. 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. On the Select Projects and Issue Types screen, you'll need to select where the issues from your old project will go. Select Software development under Project template or Jira Software under Products. Jira Service Management ; Jira Work Management ; Compass ; Jira Align ; Confluence ; Trello ; Atlas ; Bitbucket ; See. Previously when I created a new Project I was provided with 2 options ( Classic Project or Next Gen Project).