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). How can I convert it to classical type Jira Project ? Andrew Burleson, a Team Leader for 12 developers working on Atlassian’s Statuspage tool, recently moved some of his teams from Jira Software’s classic to next-gen project template and took the time to answer a few questions about the experience. Epics; Stories; Tasks; Bugs; Sub-tasks; Story Points; Epic to Stories connection; Stories to Sub. Press "Add People", locate your user and choose the role "Member" or. Under Backup for server, select Move issues and follow the instructions to move important issues over to your new server-supported. Create . You must be a registered user to add a comment. I have succesfully included the next-gen epics in the backlog view of my non-next-gen project, but when I assign one of the issues from the non-next-gen project to the next-gen epic I get an. I have already switched from next-gen projects to classic projects because I'm tired of bugs, imperfections and missing functionality, now I have no problems. I'd suggest you to read the documentation before bulk move the tickets between projects: 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. 7; Supported migration. Select Projects. Can you please give the detailed differentiation in between these two types. what permissions we need to do the same. Hi Team, I have tried to move the Next Gen Issues to Classic project. Create . jira:gh-simplified-agility-kanban and com. All users can create a next-gen project, even non-admins. Start a discussion Share a use case, discuss your favorite features, or get input from the community. Create . While our devs work to get this bug fixed, you can work around it by following the steps below: Import the CSV file into a Classic Software project instead, by following the instructions and column mapping in the documentation below: Importing data from CSV. notice the advance menu option. That is the Next Gen Roadmap Shipped section, specifically for Deployment Integration. Solved: I'd like to export all current stories from current next gen project into a newly created classic board. I'm not sure why its empty because this site is old (started at 2018). Migrating from Next-gen to Classic Software Projects Deleted user Feb 21, 2019 Is it possible to move a NextGen (kanban) project to a Classic Kanban, so that we can hook it up to the Portfolio Management?Classic project: 1. Ask the community . Where did the issues/tasks go?This year Atlassian renamed the project types to use more meaningful nomenclature. We have a JIRA service desk setup. A new direction for users. . From your project’s sidebar, select Board. The filter for the board would look like: Project in (ABC, 123) where one of those is a classic project and one is a Next-gen project. Script to migrate a Jira Classic project to Next generation project - jira-classic-to-next-gen/README. Jira ; Jira Service Management. HTML format seems the best bet to do so. It would look something like this: 1. You can find more info here:. Next-gen: Epic panel in backlog. 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 Jira Admin) whereas Next-Gen projects give more power to your Project Admin by allowing them to create their own. Have logged time show up in the Worklogs. 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? You'll need to ensure in the Next-Gen Projects you have a project role with the "Move Any Issue" permission, even if you're a Jira Admin. Ask a question Get answers to your question from experts in the community. You can now manage epics on the backlog of your next-gen project via the Epics panel, similar to how epic management works in classic Jira Software projects. Products Interests Groups . You are going to need to do some manual work. The Roadmaps feature is currently only available in Next-Gen projects. Let us know if you have any questions. The whole company is working within. 3. The choice for a classic project is gone: The whole point of choosing CLASSIC JIRA is to avoid the automatic creation of new schemes, workflows, issue types, etc. You're on your way to the next level! Join the Kudos program to earn points and save your progress. Doing a quick test, it seems that the BitBucket branches linked to Next-gen issues are kept after the issue is moved to a Classic project, although the Branch name is kept with the old issue key. You are going to need to do some manual work. Next gen projects are not a good way to work in if you need to move issues between projects. The team currently works with a company-managed project but wants to move to a team-managed project because the project admin needs to make frequent changes to the project's workflow and fields without the dependency on Jira admin. I'm afraid you have to create a classic project and then use bulk-edit to move the issues into it from the next-gen project. Next gen project: 1. Bulk transition the stories with the transition you created in step 2. choose the project you want from the selector screen. 1. Products Groups . Products Groups Learning . Let us know if you have any questions. Answer. 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). 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. Cloud to Data Center Project Move. View a list of versions, their status (released, archived, unreleased) and the progress of that version via the releases page. But not able to move the custom field info to Classic. Jira ; Jira Service Management. Hi I used JIRA Service Desk cloud for free planning, the question is my JIRA Service Desk template for Next Gen is empty. In fact, the sub-task functionality is a relatively new feature in next-gen (It was implemented two months ago as you can see in this link), so I believe our developers will be adding further improvements to it in the next months. 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. We're currently exploring how we can support next. 1. About Jira; Jira Credits; Log In. Next gen project (no board settings like columns):My PM does not like Next Gen. This name change reflects the main difference between both types — Who is responsible for administering the project. 3. I have it reported to our product team here to give the ability to use the issue navigator to return issues that are linked to a Next-Gen Epic. 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. 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. 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 ManagementSearch for jobs related to Change next gen project to classic jira or hire on the world's largest freelancing marketplace with 23m+ jobs. Moving will move an issue from one project to another and use the next key number in the target project. Is it possible to migrate a next-gen project to classic project? Thanks a lot, Gianmarco Watch Like Be the first to like this 3690 views 3 answers 1 vote Jack. Hope this information will help you. The process is a bit tedious and depends on the details of your starting point w/ the Classic project. Ask the community . Answer accepted. We performed a test migrations of a single epic, and three of it's child issues - everything went along nicely, all four issues were migrated successfully, parent links were maintained, including development tasks per issue. Best you can do is create a new project and move the issues you want into it. Need to generate User Story Map that is not supported by Next-Gen Project. If you want to create a server backup, contact support. 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 projectsLearn how to migrate users and groups with Jira Cloud Migration Assistant. We performed a test migrations of a single epic, and three of it's child issues - everything went along nicely, all four issues were migrated successfully, parent links were maintained, including development tasks per issue. Click on Move. Advanced and flexible configuration, which can be shared across projects. Here's what I see as the important details. My project was created as a classic software and I already have sprints completed, sprints ongoing + a full backlog in it. 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. Create . We have been releasing the new features and UI over the past several months and will continue to do so as quickly as we can. 4) Convert a Project to Next-Gen. Search for jobs related to Jira migrate classic project to next gen or hire on the world's largest freelancing marketplace with 22m+ jobs. I have not tried that before, but you could give it a whirl. If you've. See all events. repeat for each epic. 3. Server to Cloud. Epic links: Links between. 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". 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. If you try to move it back, it gets a new ID and still doesn't have the old data. Have a look at. If you want, select Change template to see the full list of next-gen project templates. I have created the custom fields same as in Next Gen projects. I'm trying to migrate our Classic projects over to Next-Gen, however there seems to be no way to assign a Project Type or Description to a Next-Gen project. Workflow can be defined to each issue types etc. Even more when I think about bigger and bigger organizations moving to next-gen, and facing large amounts of. Instructions on how to use the script is mentioned on the README. There is no such a concept of next-gen projects in Jira Server. It only allows issue to be changed to Epic or Story even though Subtask is clearly a defined issue type for our project. Note that, since the projects are different, some information might be lost during the process. If you've already. Use bulk move for these issues to add Epic Link to Link them to the new epic. When I was moving epic issues from next gen project to another one. you can't "migrate" precisely in that there is no 'button' to migrate. What you need to do is export the old project issues into JSON, edit the issue keys to reflect the new project key, then JSON import. All issues associated with the epics will no longer be linked to the epic. To the right under Related content you will see that this question has been answered many times now. In the screenshot below, you can see the issue TNG-8 was correctly migrated to the Project TEST (Becoming TEST-18), however, the linked branch. The Type defaults to Software for every project and I can find no field to change this, and there's no Project Description altogether. From the doc you've linked: Active sprints: Sprints in progress in your classic project won't move to your next-gen project. 3. These next-gen projects are not compatible with Jira Data Center or Server. 1. 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?. py extension and download the required " requests " module as its written in python. Click the Project filter, and select the project you want to migrate from. Issues that were in the active sprint in your classic project will be in the backlog of your next-gen project. Jira Service Management ;If you move a next gen project to to the Trash and then attempt to generate a backup for server the backup manager does not display the trashed project in the list of next gen projects but the backup for server button is still disabled. Context: We are planning to migrate a next-gen, team-managed project to a classic, company-managed project to enable more features for the customer. Move the issues from the Classic Software project to the Next-gen project: Migrate. Issues that were in the active sprint in your classic project will be in the backlog of your next-gen project. 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 . Active sprints: Sprints in progress in your classic project won't move to your next-gen project. Everything was mapped via bulk move. Also, right in the beginning of the page you can filter through the sprints, even the past ones. Products Groups . There are better tools available than "next-gen" that are cheaper and faster than Jira. i would like to switch back to classic. 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. Solved: Hi, I really like the look and feel of the next-gen projects. Products Interests Groups . Objective : I want to be able to import CSV file as a Next Gen project in Jira. If you're using Jira next-gen projects, support for JQL behaves differently compared to classic Jira projects. Project Level Email Notifications for next-gen projects on JSW/JSD; Atlassian Community Events. . Ask a question Get answers to your question from experts in the community. - Custom workflowsThought I should add a reference to the documented limitations of using Portfolio for Jira with Next Gen projects. For migration of tickets use the bull edit option in Jira. Thanks for the patience guys, any requests/comments for Estimation related functionality should be made here. Introducing dependency & progress for roadmaps in Jira Software Cloud. Migrating 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. Please review above bug ticket for details. In classic projects, Jira admins configure a project using schemes to map shared objects to projects, like issue types, workflows, fields, and permissions. For fields that are option fields, checkboxes (multiple-choice) or multiple-user fields, migration asks if I want to keep the orginial values. . Answer accepted. I can see the various export formats but they do not seem to all include the images and other attachments as part of the export. If you have tickets in a next-gen board, I assume you just bulk edit the issues and move them to a classic project, map the status and done. The functionality itself remains the same and. Mathew Dec 18,. 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. The content of the Environment variable from the next-gen project was preserved during the migration to Classic; Backup your Jira Cloud application data and Import it into Jira Server. You can easily distinguish a next-gen project from a classic project by the Roadmap feature. Ask a question Get answers to your question from experts in. In short, the settings have been stripped back to a similar level to that of the Project Admin role in a classic Jira project – with some additional extras and, at least in Atlassian’s eyes, a more user-friendly layout. Create . 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. Hi @Neil Timmerman - My understanding is that all issues in the classic project will end up in the backlog. . 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. Jira Service Management ;3. No, you have to create a new project, then move all your issues into it. Next-gen: Epic panel in backlog You can now manage epics on the backlog of your next-gen project via the Epics panel, similar to how epic management works in classic Jira Software projects. Issue-key numbers should remain the same 3. 3. I would like to make sure the issues and the issue suffix are not deleted when I dele. Is there anyway to change the project type form Next-gen software to classic type as lot of classic features are not available in the Next-gen type? Products Groups Learning . pyxis. Not unless they migrate a lot more functionality from classic into next-gen projects. csv from next-gen and then import it to classic, i've faced with issue that epics doesn't include the tasks/stories. 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. Classic Boards: You can visualise Next-Gen projects on a. Jira Work Management. Jira's next-gen projects simplify how admins and end-users set up their projects. Atlassian Support Jira Software Documentation Cloud Data Center and Server Working with next-gen software projects Next-gen projects are the newest projects in Jira Software. @Charles Tan in order to start creating Classic projects please take the next steps: 1. Regards, Angélicajust have launched test version (on cloud) of Jira Service Desk in my new company and dont find half of funcionality which I knew from previous versions of Classic Jira I used in my old company. This does allow mapping creation date. If you need additional functionality, you would need to create a Classic software project and move the issues from your Next-gen project to the new Classic project. If you change the filter associated with the board, that will affect the history of all the sprints associated with that board. Here's what I see as the important details. 1 accepted. Hi, I'm a little confused on how to add a subtask to an issue in a Next-Gen project. Ask a question Get answers to your question from experts in the community. Learn about Next-gen projects in Jira Cloud, and explore the differences between Next-gen and Classic projects. Kind regards Katja. When moving issues from a next-gen project to a classic project, you are prompted to include child issues if they were not already a part of the initial list of issues to be moved. Workaround. I started with 83 issues and now on the new board, I have 38. However, it's important to note that migration projects are typically complex endeavors and necessitate careful planning and strategic execution. Fix version, can be tagged to release. We have an established project with epics, stories, tasks and sub-tasks. Bulk move issues into their new home. 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. Migrate between next-gen and classic projects. On the other hand, Team members having only assigned privileges can move the transitions in classic. Changes you make in the panel on the backlog will reflect on the Roadmap, and vice-versa. We have a classic project with a lot of issues with subtasks. Note that, since the projects are different, some information might be lost during the process. You will have to bulk move issues from next-gen to classic projects. That would mean to auto-generate few schemes and names that are far from ideal. Is there a way to automatically pop. Your Jira admin will need to create a new classic project. Issues that were in the active sprint in your classic project. On the Project Template Key there are the following options that are the next-gen ones: com. . Create a regular project and move the issues from the Next-Gen Project to the newly created project. There are four types of possible migrations: 1. Click on the ellipsis at the top right. There is no option to do that. 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). Jira Service Management ; Jira Work Management ; Compass ;. Recently started working for a Fintech where there a number of open projects. Hi, I migrated issues and tasks from a Classic Business Project to a NextGen Project. . . We are using custom fields in the classic project and which we recreated in the next-gen project. Try this to bulk move in the Next Gen version: Go to the project with the tasks you want to move. Ask a question Get answers to your question from experts in the community. When Issue moves from Next-gen to a classic project, the sprint ID will still exist. Search in the marketplace. WMS Application to AWS). Issues missing after migration to new project. If you google it you will get to know more about bulk edit feature. This is because of the below bug: [JRACLOUD-70949] CSV import will fail if Next-gen custom field is mapped. move all issues associated with an epic from NG to the classic project. In next-gen projects, the only way currently to see sub-tasks on a board is to use the group by function. We want to transfer all the Jira issues of a project from the Next Gen Cloud version to a server version. Do we have any data loss on project if we do the project migration from nexgen to classic project. Ask the community . Create . Hello. Create . We have several departments tracking tickets and each dept cares about certain things (custom fields). On the next-gen templates screen, select either Scrum or Kanban. Are they not available in Next-Gen/is there some other configuration. You cannot change out Workflow Schemes for Next-gen Projects. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. I really find the next-gen UI difficult and weak compare to classic UI. Several custom fields I have in Next Gen are not in classic. Click the Jira home icon in the top left corner ( or ). Create . But for projects that need flexibility, Next-gen simply is not ready. Ask the community . How can fields be added here? C. Your site contains next-gen projects. The columns on your board represent the status of these tasks. As with 1 I made sure that all the columns that existed in my classic project had a counterpart in the next gen project, and in the migration wizard I selected the appropriate mappings in step 3 of 4. This does not mean the end of classic Projects or the Jira Admin role for that matter. Can I. You can select Change template to view all available company-managed. This document should help you out - migrate-from-an-next-gen-project-to-a-classic-projectRegarding your second question, you can bulk move your tickets from next-gen to a classic project. 3. You're on your way to the next level! Join the Kudos program to earn points and save your progress. It appears that the System External Import does not support Next Generation projects. 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. The specific steps would be: - Navigate to your classic board > Click on the three dots Icon > Board settings > Edit filter query. This is. Startup the script and follow the prompt to correct the Epic Links in your next-gen Projects. 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. This script copy following data from classic project to next gen project. Just save the file with a text editor in a . " So, currently there is no way to create a custom field in one project and use it in another. . . Hope this helps! You must be a registered user to add a comment. You could consider migrating your issues from the NG to a Classic. LinkedIn; Twitter; Email;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. Ask the community . If you use Jira Software Cloud, check out this article to learn about creating a next-gen Scrum or Kanban project. Patricia Francezi. If you use Jira Software Cloud, check out this article to learn about creating a next-gen Scrum or Kanban project. If you do bulk changes in Jira, it is always a good thing to take a backup before it. Add the permission to Schedule Project for any roles/groups/users you want to manage and work the sprints. Click your Jira . Products Groups . I dont seem to be able to create them in classic. Is it possible to switch/migrate to classic version to show in my new company all features of Jira? Unfortuntely, it's clear Next-Gen is not suitable. Next-gen projects include powerful roadmaps and allow teams to create and update. :) I am going to. Next-gen projects and classic projects are technically quite different. In issue type,can easily drag and drop the JIRA fields. Migrating issues from Classic to Next-Gen. Built and maintained by Atlassian, the app is free to install and use. After seeing those fields, I went into the settings and added the ones i wanted to keep as Custom Fields. com". Thanks in advance for any help you can provide. Startup the script and follow the prompt to correct the Epic Links in your next-gen Projects. From your project’s sidebar, select Board. - Back to your board > Project Settings > Columns. A project is started there as an experiment. The problem is that the two projects will have different workflows and not a part of the same workflow scheme. Migrate between next-gen and classic projects; Related content. Some of the instructions were a little out of date but overall it was very helpful in getting me to the right place. Solved: I would like to convert a classic software project into a next-gen project in order to use the roadmap feature. We created a project with names we quickly abandoned once we figured out how the Next-Gen project worked; however, when we go to perform a bulk operation the initially rejected names are the names on the columns, not. Thank you for mentioning Deep Clone for Jira, @Ismael Jimoh . Yes, you can disable the. cancel. Next-gen projects include powerful roadmaps and allow teams to create and update their issues. The content of the Environment variable from the next-gen project was preserved during the migration to Classic; Backup your Jira Cloud application data and Import it into Jira Server. I know a LOT of people have had this issue, asked. md file on the Repo. Is there anything I need toWe'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. Hi, I miss the point of these features since they already exist in classic projects. 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. Do read the Things to keep in mind if you migrate from classic to next-gen thoroughly before you make the move! You must be a registered user to add a comment. For more information on global permissions, see Managing global permissions. Caveats when using a Custom Field and a System Field with the same name. Watch. I am able to migrate. Ask a question Get answers to your question from experts in the community. Navigate to your next-gen Jira Software projec t. 2. Display all the child issues in both new and old issue view. Ask a question Get answers to your question from experts in the community. 2. I am trying to get the same epic & stories within that epic to appear in both a classic Jira project view and a next-gen project view The issues are created in the next gen project and appear there just fine. 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). prashantgera Apr 27, 2021. Move them to the same project but the 'epic' typeThis Project has 5000+ Issues and I need to migrate it to our Production instance. In a nutshell, you'll have to create a new Classic project to receive your tickets, then query and (bulk) move the issues from you existing next-gen Project. Expected Results. The system will open the Bulk Operation wizard. Jira asked that I should move child issues also, After child issues were moved successfully I realized that epics hadn't moved and there not in the original either. Yes, you are right. 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. When we think about the Next-Gen project experience, these are the key new features: Roadmaps ; Customizable, drag-and. Ask a question Get answers to your question from experts in the community. Then I can create a new Scrum Board based on this filter, and those tickets. NG-2 -> OLD-100; View a board on. Create . I have inherited a project which was originally set up on a 'classic' JIRA board. The prompt wouldn’t show up if you are already moving all the child issues along with their respective epics at the same time. Cloud Data Center and Server Get started with next-gen projects Create a next-gen project All users can create a next-gen project, even non-admins. I can add primary and secondary fields (appears in the upper and lower right pane), but fields that appear in the main view - between the left and the right pane - can't be added/changed. The documentation on workflows in next-gen projects has been updated lately: Sep 17, 2020. repeat for each epic. Choose 'move': 3. I have been charged with setting up a project for a project for a fairly simple team migrating from Rally to Jira. Zephyr is a plugin for Jira, which handles test management. . 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. 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". Doing a quick test, it seems that the BitBucket branches linked to Next-gen issues are kept after the issue is moved to a Classic project, although the Branch name is kept with the old issue key. in the far upper right corner, click on the "meatball menu" - the three dots. Or, delete all next-gen projects and their issues outright. Solved: Hi, I am investigating if I can transition my Classic Service Desk project to a NextGen project. Next-gen projects and classic projects are technically quite different. I'd suggest you to read the documentation before bulk move the tickets between projects: Migrate between next-gen and classic projectsHi, Colin. Products Groups . 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. Most data will not transfer between projects and will not be recreated see. Products Groups Learning . I couldn't find the next-gen template when trying to create the new service desk, and. JCMA lets you migrate a single project. I don't think it's mature enough to be in the market and frankly if there were a convenient way to migrate away from Jira entirely I would do so. If this question is still relevant for someone, see the detailed documentation for the specified method, it looks like it can move issues from the backlog to the board. Epic links: Links between. We naturally hear how Classic Settings brings back missing options (and we love it!), but offering next-gen project admins a time saving alternative for essential configuration needs is definitely a plus worth mentioning. This is managed by agents. Details on converting the project is covered in the documentation at "Migrate between next-gen. 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. You can migrate from next-gen to classic. When generating your backup, if there are any next-gen projects in use, it will ask you to move these issues to a standard project. While our devs work to get this bug fixed, you can work around it by following the steps below: Import the CSV file into a Classic Software project instead, by following the instructions and column. 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. 1. We have occasion to move tickets from a classic project to a next gen project, but there is a custom field we added to the source and target issue.