. Migrate Jira users and groups in advance ROLLING OUT. In JIRA next-gen projects, any team member can freely move transitions between the statuses. Create . Please kindly assist in. 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". If you are planning to import cloud backup into server then first you have to migrate next-gen issues into classic projects and only then you can import the cloud backup into server. Currently, that tool causes several bugs: All issue types are forced to type 'Story' or 'Task' Story points are removedYou can follow the steps of the documentation below to migrate from Classic to Next-gen. The solution here would be to use an Automation Rule (Global Rule for all Team-Managed projects or a Team level Rule) to auto-set the Resolution field when transitioning an issue for Jira Issues transitioned to a Done Status moving forward. It's native. 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. But please understand that this form of migration will delete the user accounts in LDAP and add them to Jira internal. I'm trying to use the REST API to search all issues in the Project that have ever been a different issue type. Ask a question Get answers to your question from experts in the community. net. Hello, You should have read the guide for migrating next-gen to classic. However, boards across multiple projects cannot be migrated automatically. 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. I have inherited a project which was originally set up on a 'classic' JIRA board. Turn on suggestions. the only problem is that when you report, the. A set of helper tools for importing issues from a classic Jira project into a next-gen project. You can add it like. Ask a question Get answers to your question from experts in the community. 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. Dear All, Is it possible to migrate a next-gen project to classic project? Thanks a lot, Gianmarco. In other words do the following: create new epics in new classic project; move your epic children one epic at a time and then using bulk edit assign the epic link for those issues to the new epic; rinse and repeat. Jira ; Jira Service Management Jira Align. You're on your way to the next level! Join the Kudos program to earn points and save your progress. - Add the statuses of your next-gen issues to the columns of your board. When you integrate Aha! Roadmaps with a Jira team-managed project, Aha! Roadmaps will automatically detect the template type and create appropriate field. The reason this is difficult is because the configurations between the two projects need to be essentially identical. I know I have to perform a manual install and can really use any documentation that explains the best way to migrate from Jira v7. Ask the community . Teams break work down in order to help simplify complex tasks. 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). The prompt wouldn’t show up if you are already moving all the child issues along with their respective epics at the same time. There are better tools available than "next-gen" that are cheaper and faster than Jira. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Click NG and then Change template. We’ll keep you updated on their progress. Feel free to ask any questions about. 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. To see more videos like this, visit the Community Training Library here . When I move the issue form Next Gen to Classic it clears those fields. Avoid passing through a proxy when importing your data, especially if your Jira instance. md at master · maknahar/jira-classic-to-next-gen Next-gen projects and classic projects are technically quite different. Turn on suggestions. 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 the difference between classic and next-gen projects. Airbrake Integration with Next Gen Project? I'm struggling to make an integration with Airbrake, but not works. Unfortunately, as Stuart noted above at this time, Advanced Roadmaps does not support next-gen projects, and will only work with the classic project types, so you will need to plan out which projects you want to see in the Advanced Roadmaps plans in advance and convert any Next-Gen projects to classic projects to make this happen, details on. This year Atlassian renamed the project types to use more meaningful nomenclature. Create a classic project and set up a workflow in that project. When using CSV import the only field that seems related is Parent-ID. Ask the community . It's Dark Mode. 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. When I try to create a new project I am given a choice whether to select Classic or Next-gen project. 2. The prior class of projects was called classic, so this is what we all get used to. Moving epics and issues manually from UI is cumbursome and time consuming. 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. Understanding Issue Types in Jira; What are Issues in Jira; What’s the difference between a kanban board and a Scrum board? New Portfolio Cloud Experience Beta; Announcement: Project Level Email Notifications for next-gen projects on JSW/JSD1 - Sign-up for a brand new JIRA Server instance. Click the Project filter button and choose the project you want to migrate from. Ask the community . Ask the community . We have a complex predominantly Classic implementation of JIRA with multiple teams and projects. Keep in mind some advanced configuration could be lost in the process because the new version does not support them at the time. Converting from Next-Gen back to Classic. Thanks for the patience guys, any requests/comments for Estimation related functionality should be made here. So what’s the. OSLC Connect for Jira allows you to navigate directly to the DOORS asset with just a click!As far as I see it is not yet possible in the next-gen projects to assign a card color to a label. Migrate between next-gen and classic projects; As John said, you need to create a new project, it's not possible just to change the project type, so after that, follow the steps of the documentation. Jira does not support CSV import facility in next gen project. Would like to have a check whether will have any data loss related to user management or on access control after doing the migration. Procurement, Renewals, Co-terming and Technical Account Management. Ask a question Get answers to your question from experts in the community. How can I migrate from next-gen project to classic scrum project. To delete a field, again it depends on whether it is Classic or Next-Gen. Next-Gen is still missing working with parallel sprints, etc. 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. In This support article currently available strategies and workarounds are listed. I need to be able to have the classic projects to Next Gen so I have access to those custom fields. 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. First, developers can now create issue fields (aka custom fields) for next-gen projects. com". 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. I tried moving issues from a classical project to a next-gen project. 2. On the next screen, select Import your data, and select the file with your data backup. Is there a way to move to classic without starting the project over? Regarding your second question, you can bulk move your tickets from next-gen to a classic project. Next-gen projects are now named team-managed projects. Products Interests Groups . To create a backup for server, either: Bulk move important issues from next-gen projects into classic projects administered by schemes. Hello Sarah, Welcome to Atlassian Community! 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. Search for jobs related to Migrate to jira next gen project or hire on the world's largest freelancing marketplace with 23m+ jobs. notice the advance menu option. This Project has 5000+ Issues and I need to migrate it to our Production instance. there's no way to swap a project between Classic and Next-gen. 1 answer. I dont seem to be able to create them in classic. Hi, Colin. Products Groups . I can do this for individual issues, but I would like to see all that were a Bug, or an Epic, and so on. Now the user could see the values “Epic” (Classic), “Epics” (Next-gen), or “Rachel’s Super Special Epic” (Next-gen) when they query. Atlassian Support Jira Software Documentation Working with next-gen software projects Cloud Data Center and Server Get started with next-gen projects Create a next-gen. Issues that were in the active sprint in your classic project. You can create a workflow rule not to allow stories to move from one swimlane to the next. 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. If that's the kind of thing you want to do, I would suggest you use Classic Software projects to perform that function as they can use shared fields across those project types. . I'd like to export all current stories from current next gen project into a newly created classic board. You can find instructions on this in the documentation. Thanks for the patience guys, any. Scrum is a more prescriptive methodology that provides a structured framework for planning and executing projects. If you are in a situation where you need to migrate projects with thousands of issues, it is physically not possible. Generally speaking, I would aim at building a new Jira, creating new schemes and configurations and then just importing issue/comments/whatever else you need. The only solution offered to "migrate" is to move and remap all the issues from a classic project to a next gen project. 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. 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. py extension and download the required " requests " module as its written in python. I have been charged with setting up a project for a project for a fairly simple team migrating from Rally to Jira. Move them to the same project but the 'epic' typeJira Cloud here. You can now create smaller pieces of work, with a single click, right from the Jira roadmap. Benefits of migrating to Jira Service Management from Halp; Requirements for using the Halp migration tool; Migrating from Halp to Jira Service Management. Your site contains next-gen projects. However, you can manually move your issues via bulk-move. I have created the custom fields same as in Next Gen projects. click on Create new classic project like in the picture below. I'm using Jira Cloud and did a bulk move operation in order to migrate issues from a next-gen project (TCC) to a newly created classic project (TCLOUD). If you need a customized workflow, Classic projects are where you want to be for now. Boards in next-gen projects allow you to. Script to migrate a Jira Classic project to Next generation project - jira-classic-to-next-gen/README. Appreciate any help!!! Track and manage all aspects of your team's work in real time from the convenience of your iOS or Android device with Jira Cloud mobile. Depending on the. Start a discussion. Have logged time show up in the Worklogs. 5. 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. Hope this information will help you. 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. Adding these custom fields -- along with the recent roll. 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. . thanks for this tip ! There is a plugin to move projects, but I don't know if it works in the cloud. . You can bulk move issues from next-gen to classic projects. Select the issues you want to migrate and hit Next. md file on the Repo. XML Word Printable. In the top-right corner, select. You are going to need to do some manual work. 3. Products Groups. atlassian. Check out this post and read the "Things to keep in mind if you migrate from next-gen to classic" section if you plan to do so. 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. Start a discussion Share a use case, discuss your favorite features, or get input from the community. Indeed it's possible bulk clone up to 5000 issues between classic and next gen projects with our app. I want to migrate to classic because I'm deeply dissatisfied with the "next-gen" product. I need to add roadmaps to my Jira software project and link backlog user stories to epics from the roadmap. Issues are the heart of Jira. Ask the community . Before I migrate our issues over to the new classic board I wanted to test it out before moving my team over. 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. Issues that were in the active sprint in your classic project. I would recomend watching This Feature Request for updates. You must be a registered user to add a comment. This change impacts all current and newly created next-gen projects. Converting won't be possible, you'll have to migrate the project to a new one. On the Map Status for. You can migrate application server and start application. The team took this matter to the board and decided to rename Next-Gen and Classic. Create . atlassian. 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. To change a story to a task etc I just click on the icon next. Or, delete all next-gen projects and their issues outright. Jira Work Management ; Compass ; Jira Align ; Confluence ; Trello ; Atlas Bitbucket ; See all. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Jira Service Management. e. 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. Hey Ollie - I just encountered a situation with a customer where they were trying to integrate a Next Gen project via the Jira connector with Jira Align. Host and manage packages Security. Go through the wizard, choose the issues that you want to move and click Next. If you don’t want to use a product after migrating, use a free plan, or start a 7-day trial for that product. Ask the community . It would look something like this: 1. This Project has 5000+ Issues and I need to migrate it to our Production instance. 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. 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". 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. If you are in a situation where you need to migrate projects with thousands of issues, it is physically not possible. Now, migrate all the tickets of the next-gen project to that classic project. The documentation on workflows in next-gen projects has been updated lately:Using TM4J for our test cases in Jira Next Gen and Classic Projects. 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. Create . The Windows 2003 installation was installed on the C drive the Windows 2012 server will be on a E drive I have reconfigured the following files to take into account the fact Jira is on the E drive and pointing to another SQL serverHi, We have a custom field for Engineering Priority that is on Zendesk tickets. Portfolio for Jira next-gen support. 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. We’ve added a new card to the Jira Cloud Migration Assistant home screen that lets you migrate Jira users and groups before project data. If you're. repeat for each epic. Jira Work Management ; Compass ; Jira Align ; Confluence. 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. Next-gen projects are independent of other next-gen and classic projects, so the custom fields, workflows, permissions are not shared between them. Next-gen projects and classic projects are technically quite different. Exporting worklogs is only needed in cases where you have worklog attributes configured or if you have not migrated the worklogs to Jira Cloud with the Jira backup. But I'd rather not have to migrate and then migrate back again if we change our minds about using the next-gen project. Ask a question Get answers to your question from experts in the community. Ask the community . Create . Introducing dependency & progress for roadmaps in Jira Software Cloud. 5. Search in the marketplace. Classic has the option to setup automation with Automation and Project Automation, but Next-gen only has the option for Automation. Products Groups . In that stage instance, I have created a Classic Project with the same fields as the NextGen Project and tested a few (3. Thank you for mentioning Deep Clone for Jira, @Ismael Jimoh . This allows teams to quickly learn, adapt and change the way. I am unable to provide any comparison. The first theme is that people want roadmaps in classic projects. Ask a question Get answers to your question from experts in the community. The Fix Version is actually the built-in one. The ability to create Next-gen projects is enabled for all users by default. g. Hence it seems this field is only for sub-tasks. In classic projects, Jira admins configure a project using schemes to map shared objects to projects, like issue types, workflows, fields, and permissions. Log time and Time remaining from the Issue View. 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. Automation for Jira is a game-change r enabling teams to be more autonomous, by providing an opportunity to customise their process and workflows. If you have an existing Jira Software project, it probably isn't a Next-Gen project. Solved: Hi team, I have one Next -gen project in cloud. It will involve creating a new Classic project and bulk moving all of your issues into it. 2 - follow the documentation below to properly migrate your current JIRA Cloud site to the Empty Server instance: Migrating from Jira Cloud to Server. 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. Ask a question Get answers to your question from experts in the community. I am trying to bulk move issues from my classic project to a next-gen project. The specific steps would be: - Navigate to your classic board > Click on the three dots Icon > Board settings > Edit filter query. atlassian. My question, what is the easiest and cleanest way to migrat. - Add your Next-gen issues to be returned in the board filter. Atlassian Licensing. But information on the custom fields are lost during this transition. About Jira; Jira Credits; Log In. 1 accepted. The Roadmaps feature is currently only available in Next-Gen projects. 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. After seeing those fields, I went into the settings and added the ones i wanted to keep as Custom Fields. I try to to include tasks from a nextgen kanban project (chris test again) into a classic software scrum board (chris test) sprint. A quick way to tell is by looking at the left sidebar on the Project Settings section. Next gen to classic migration . In the top-right corner, select more () > Bulk change all. Ask a question Get answers to your question from experts in the community. Classic projects are now named company-managed projects. This name change reflects the main difference between both types — Who is responsible for administering the project. The next-generation convenience images in this section were built from the ground up with CI, efficiency, and determinism in mind. I migrated a project from Jira Next-Gen to Jira Classic. 3. Select a destination project and issue type, and hit Next. - Add the statuses of your next-gen issues to the columns of your board. . Alexey Matveev Rising StarMigrating Jira projects from Next-Gen to Classic Giovanny MACARTHUR Apr 07, 2021 Team, We are looking to move from Next-Gen to Jira Classic but have a. This gives the same options as in a classic project to upload a csv. It would be my expectation that all comments are migrated from the ticket in Classic Jira to Next. you should then see two choices: Classic and Next-gen. Jira next-generation projects. For example: Epic links and issue links: Any issue links in your classic project will not exist in your. . 1. Meanwhile, I've tried multiple ways to migrate back to classic, yet the Description. If you've already registered, sign in. Your Jira admin will need to create a new classic project. Next-gen projects are now named team-managed projects. Jira Cloud; JRACLOUD-78620; Migration tool from company-managed (formerly classic) to team-managed (formerly next-gen) project and vice-versa. Mainly because the inability to share custom fields across projects and the link to Jira Align apparently works much better with Classic. The Next-Gen is an individual project, designed to be more straightforward than the classic Scrum and/or Kanban template, with a single board, simple workflow and limited field options to be used at the issue detail view, this includes that issues from your Next-Gen project will only be available inside of that project, you shouldn'thave. Sprints are associated to agile boards, not to projects. 3. Issue-key should remain the same. However, you can move all issues from the classic project to the next-gen. Is it possible to upgrade existing "classic projects" to. migrate between next-gen and classic projects . Script to migrate a Jira Classic project to Next generation project - jira-classic-to-next-gen/README. Cloud-to-cloud migration helps you move users and Jira Software, Jira Work Management, and Jira Service Management projects from one cloud site to another. Create . Keep in mind some advanced configuration. In the top-right corner, select Create project > Try a next-gen project. 1. Migrate Jira to a new server. 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. If I understood correctly, the goal of Next Gen was to simplify JIRA, namely: how workflows, custom fields, custom screens, permissions, etc. You can migrate from a next-gen project to. 2. Kanban is a more flexible. Migrating from Halp to Jira Service Management. While moving fields are getting moved but the values are missing for custom fileds. Create . For example, for bug fixing tasks using Kanban and for the new feature type projects to use Scrum. First, you need to create a classic project in your Jira Service. when click "Test integration", then it creates test issue. Firstly, on Jira, export is limited to 1K issues. 5 - 7+ seconds to just open a ticket from the board. So, the first. Jira Service Management ; Jira Work Management ; Compass ; Jira Align ; Confluence ; Trello ; Atlas ; Bitbucket ; See all. Through the ticket, they can access your site in order to help you with the migration. But if it is only the features covered in the KB above that you are missing and the portfolio application is accessible then converting the projects to classic would be the way to go, and details on converting a next-gen project to a classic project can be seen at the link below: Migrate between next-gen and classic projects The only way to convert next-gen project to a classic project is to create a classic project and move all issues from the next-gen project to the this classic project. However, I don't have experience with Classic Software projects and am afraid of possible disadvantages I'm not seeing. And now I'm stuck with about 100 projects which are hard to manage and worst of all I'm unable to add Next-gen projects are now named team-managed 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. Next-Generation Jira Projects are an Atlassian Cloud feature designed to allow teams to collaborate on projects. Regards, AngélicaHi, I have several service desks at this time all setup with Classic Jira Service Desk. 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. Classic projects provide more filters that you can configure within the board settings based on JQL filters. 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. We are using custom fields in the classic project and which we recreated in the next-gen project. 1) Use the project export/import feature. Next-gen was built to beat the competition, not to compete with Classic. I was advised by our support team that Next Gen projects are not supported via the Jira Connector at this time. About Jira; Jira Credits; Log In. This report is awesome in Jira Classic, but it really needs to be applicable to epics, and maybe even other groupings in addition to versions. It's free to sign up and bid on jobs. . You must be a registered user to add a comment. Classic projects are now named company-managed projects. Answer accepted. One of the ‘crowd favorites’ was the native roadmap, which allows teams to sketch out the big picture quickly. The new names of the projects are: Next-Gen Projects to Team-Managed ProjectsJCMA’s features resemble Configuration Manager, a popular Jira project migrating app: not only do you choose the projects to migrate, but also specific users and groups. I already tried to move the issues directly from next-gen to Classic-Jira project. Solved: Hi, I really like the look and feel of the next-gen projects. Now, migrate all the tickets of the next-gen project to that classic project. Click on "setting" icon located at right hand site of corner -> then click on "Applications" -> then click on "Jira Software configuration" -> in Features enable tick on " Parallel Sprints". Then, in the top-right corner, select more (three-dot sign) and Bulk change all. One of our teams/projects is migrating over to Next Gen. If you're looking at the Advanced searching mode, you need to select Basic. Since Deep Clone offers also some more advanced cloning options you might not have to update data after cloning. Maybe it is interesting to know that Atlassian is currently working on a migration assistant to facilitate cloud to cloud migrations. 2 - Export your JIRA Issues and projects to a CSV file and import it in Freshdesk using the Customer Import Tool. You can import your data to the classic project and then migrate data between classic and next-gen projects using the free solution from Jira Service Management. Script to migrate a Jira Classic project to Next generation project - File Finder · maknahar/jira-classic-to-next-gen. We are evaluating to migrate from Trello to Jira next-gen, so it would be great if we could continue to use Screenful, it is a great app and it really solve the gaps of Trello for sprint handling and. Click on Move. JCMA is available for Jira 7. Overall it sounds like there could have been an issue installing. Alex Nov 25, 2020. Jakub Sławiński. Search for jobs related to Jira migrate classic project to next gen or hire on the world's largest freelancing marketplace with 22m+ jobs. You will have to backup and restore attachments separately at filesystem level from the source host server to the target host server, either before or after import of XML data. Both Scrum and Kanban templates of Next-gen projects have the exact same features and possibilities. Add the permission to Schedule Project for any roles/groups/users you want to manage and work the sprints. It seems like something that would save a lot of people discomfort/stress. Next-Gen Project/Board: For Next-Gen, both board and backlog are visualised in the backlog screen. Best you can do is create a new project and move the issues you want into it. Jira Issues . Log In. I have been charged with setting up a project for a project for a fairly simple team migrating from Rally to Jira. Is there another way of doing this that doesn't require the user to add Smart Commit #transition-name ? Is this coming to Next Gen projects?Migrate Jira to a new server. Select Projects. Use bulk move for these issues to add Epic Link to Link them to the new epic. On the Select destination projects and issue types screen, select where issues from your old project will go. View More Comments. 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. You could migrate users from a delegated LDAP directory to the Jira internal directory as per the instructions in Migrating users between user directories . existing project configurations from one instance to another via Project Snapshots. Hi, Am trying to migrate jira cloud to on-prem. Services. You would need to migrate between next-gen and classic projects first and then flip back to next gen projects after the migration. If you found this video tutorial helpful, you can learn more by enrolling in our comprehensive, hands-on training course (Jira Administration Part I) at Atlassian University. 1. 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. 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. Hi, I am just starting with Jira Service Desk, and it would be better to start with next-gen project instead of classic project. The function are still limited compared to classic project at the moment. . On your Jira dashboard, click Create project. Issue Fields in Next-gen Jira Cloud. 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 you have to go down the splitting route for some reason, there are basically two options. brooks Mar 08, 2021 I've started the migration process but it seems I am going to lose all my my sub-tasks.