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). Features for next-gen projects are indeed still "work in progress", there is still lots of idea to implement - judging from public tracking system "jira. Products Groups Learning . Since the launch of Next-Gen last October of 2018, the name was found confusing. And lastly, migrate data between classic and next. Ask the community . Hi, @maknahar really handy project! It's shocking Atlassian themselves don't provide the bare minimum for this very common use case (no news here…) Are you. The process. Turn on suggestions. How, with the next generation Jira, can I have a custom f. move all issues associated with an epic from NG to the classic project. Thank you for mentioning Deep Clone for Jira, @Ismael Jimoh . Upwards of 4 second lag when trying to just click and drag a card/ticket across columns. Regards, AngélicaHi, I have several service desks at this time all setup with Classic Jira Service Desk. We have a complex predominantly Classic implementation of JIRA with multiple teams and projects. On the other side… we now must migrate to Company-managed projects (former Classic) as your progress on Next-Gen roadmap did not move forward as much when it comes to our needs. Things to keep in mind if you migrate from classic to next-gen. If I create a filter using this query: project in (pfw, ppiw) This returns all of the tickets in those projects. :) I am going to. Hello, I'm switching our project from Next Gen to Classic. atlassian. You can use this method to combine data across two or more cloud sites. The names were updated from “Next-gen” projects to “Team-managed” projects and “Classic” projects to “Company-managed. Start a discussion Share a use case, discuss your favorite features, or get input from the community. Log time and Time remaining from the Issue View. How do I do that? Products Groups . As Atlassian recently announced, they made the app custom fields available to instances enrolled in the Jira Cloud Vendor First Release program on June 24th. 2. When i migrated, all issuetypes became either Story or Sub-task. For example, I have a rule that says that a story cannot move from To Do -> In Development when the "Requesting Customer". You will have to bulk move issues from next-gen to classic projects. atlassian. Migrating from Halp to Jira Service Management. However, you can move all issues from the classic project to the next-gen. md at master · maknahar/jira-classic-to-next-gen Next-gen projects and classic projects are technically quite different. 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. Products Groups Learning . If you select the option to keep the data, the next time you enable Zephyr for Jira, the pre-existing data will be associated with the Test issue type mapped. It is written there that: Active sprints: Sprints in progress in your classic project won't move to your next-gen project. You can create a workflow rule not to allow stories to move from one swimlane to the next. The process is a bit tedious and depends on the details of your starting point w/ the Classic project. Keep in mind some advanced configuration could be lost in the process because the new version does not support them at the time. com". 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. In the top-right corner, select more () > Bulk change all. . Another way to migrate Jira is by doing a regular Site Import. 1 answer. Please help me to find reason to keep use JIRA and not move to another alternatives. - Back to your board > Project Settings > Columns. Jira team-managed projects (formerly next-gen and classic) are designed to support smaller teams. 4. Setup and maintained by Jira admins, company-managed. Is it possible to upgrade existing "classic projects" to. However, as a workaround for now. File Finder · maknahar/jira-classic-to-next-gen. For migration of tickets use the bull edit option in Jira. 1. 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. Next-Generation Jira Projects are an Atlassian Cloud feature designed to allow teams to collaborate on projects. Click on Move. md at master · maknahar/jira-classic-to-next-gen0:00 / 1:55 • Introduction How to Migrate Classic to Next-Gen Project in Jira Service Management? Help Desk Migration 379 subscribers Subscribe 0 Share 94. But the next-gen docs about sprints don't mention this. If you’re moving from a team-managed project using epics, issues on this page will be grouped based on which epic they belong to. Script to migrate a Jira Classic project to Next generation project - jira-classic-to-next-gen/README. Jakub Sławiński. net), and I am willing to migrate my boards with all existing data from xyz. However, there was a lot of comparisons between Classic and next-gen as they both lived within Jira. I've created a project with the "New generation" tools but the functionnalities finally do not fit my actual needs. If you would like to wait a little bit longer, the Jira Software. In classic projects, Jira admins configure a project using schemes to map shared objects to projects, like issue types, workflows, fields, and permissions. Meanwhile, I've tried multiple ways to migrate back to classic, yet the Description. . I try to to include tasks from a nextgen kanban project (chris test again) into a classic software scrum board (chris test) sprint. 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 must be a registered user to add a comment. Create and assign an issue to a particular fix version. . To change a story to a task etc I just click on the icon next. Currently next-gen projects are not available on Jira server. 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. I'm trying to migrate data from next-gen to classic and when exported . Create the filter and scrum board in the project in question and organize your cards into sprints. The team took this matter to the board and decided to rename Next-Gen and Classic. 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. Your site contains next-gen projects. Comment;The Next-Gen Project board looks amazing and alot less cluttered than the standard SCRUM/Agile Sprint board we are currently used to having on Jira. Hello, We are trying to migrate data from to another JIRA version hosted in our AWS Ver 7. The same story with sub-tasks, they are imported as separate issues. Jira Software Cloud; JSWCLOUD-17940; After migrating from Classic to Next-Gen it's not possible to bulk edit epic links. By default, Jira will automatically select a project template you've used previously. However, you can manually move your issues via bulk-move. 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. Please note that in some cases not all fields can be cloned. Let us know if you have any questions. Create . Migrate Jira to a new server. Here are some of the highlights: Faster spin-up time - In Docker terminology, these next-gen images will generally have fewer and smaller layers. Kanban: The main difference between Scrum and Kanban is their approach to planning and execution. This will help teams move faster, by doing. Navigate to the Next-gen Configuration page: Project settings → Apps → Nex-gen Configuration. Would like to have a check whether will have any data loss related to user management or on access control after doing the migration. Jira Service Management ;Hi @Jenny Tam . Note: These templates are coming to classic projects soon. 1. On the next screen, select Import your data, and select the file with your data backup. Jira Work Management ; Compass ; Jira Align ; Confluence ; Trello ; Atlas Bitbucket ; See all. The prompt wouldn’t show up if you are already moving all the child issues along with their respective epics at the same time. Migrating from Halp to Jira Service Management. Very surprised by this oversight, and that a list of features that aren't included weren't added to the migration documentation. Select Move Issues and hit Next. The Jira Cloud Migration Assistant is an app that helps you easily move projects, users, and groups from Jira Core or Jira Software on server to the cloud. 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. Currently Next-Gen Projects do not support the parent child relation ship that allows the higher initiative levels in Portfolio for Jira. We could move this into Jira as a custom field but from what I understand now, with the next generation, this Jira level field cant be brought into the projects. Jira ; Jira Service Management. Basically what you will be doing is installing Jira on your Windows server, do a xml backup on the Linux one, restore it on Windows and then move attachments and re-apply any modifications you have done. Classic provides an option to setup a simplified status label for the customer's view, while Next-gen does not. It's Dark Mode. Solved: Hi team, I have one Next -gen project in cloud. First, you need to create a classic project in your Jira Service Management. Boards in next-gen projects allow you to. Atlassian Licensing. 3. For each task, it takes me about 5 clicks, including finding the right parent task from a list of poorly numbered tasks, from the roadmap view, and then I can't see the subtasks on the roadmap, so I have to go to the advanced roadmap to see. 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. To create a backup for server, either: Bulk move important issues from next-gen projects into classic projects administered by schemes. For example, I have a rule that says that a story cannot move from To Do -> In Development when the "Requesting Customer". Introducing subtasks for breaking down work in next-gen projects. There is no Epic-Link field like there is in Classic mode. Since then, many of. Then I decided to start from scratch by creating a new project with the "Classic" type. Based on our research, we know that this often starts as just. We have two types of projects: company-managed and team-managed (formerly known as classic and next-gen) projects in Jira Software Cloud. Click the Project filter, and select the project you want to migrate from. Click on the 'issue types' option in the project settings' menu. 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. Problem Definition Presently, anytime you convert a project between Next-gen and classic (or vice versa) the epic relationship between. 8 URL: We are trying to consolidate multiple JIRA instances into one instance at the enterprise level. From your project’s sidebar, select Board. If you have an existing Jira Software project, it probably isn't a Next-Gen project. Once you choose to add the issue to the board (drag-and-drop. Before we make that migration, we need to know if the history will migrate Atlassian. 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 typesMigrating from Halp to Jira Service Management. 3 - If you have developer resources, you can build an API connection into your Freshdesk account to import ticket data. net) and we are buying another domain (eg. It's free to sign up and bid on jobs. You must be a registered user to add a comment. Turn on suggestions. If you have to go down the splitting route for some reason, there are basically two options. 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). The ability to create Next-gen projects is enabled for all users by default. As a workaround, you may want to try to import the issues into a Classic project and then migrate them to a Next-Gen project as explained in: Migrate between next-gen and classic projects . Then when i go back in my project I have an Issue tab that appeared. Jira Next-Gen Issue Importer. Ask a question Get answers to your question from experts in the community. 3. Ask a question Get answers to your question from experts in the community. Things to keep in mind if you migrate from classic to next-gen. xml file in the home directory that contains the db data, for confluence its in the confluence. Jira's next-gen projects simplify how admins and end-users set up their projects. Jira Software; Questions; Migrating from Next-gen to Classic Software Projects; Migrating from Next-gen to Classic Software Projects . Click NG and then Change template. 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. . Solved: As i dont have many important features like, add work log, time estimation, add sub tasks, etc. Click the Project filter, and select the project you want to migrate from. You can create a workflow rule not to allow stories to move from one swimlane to the next. Data loss related to projects , comments or description related to the issues or on the state of the issues. Answer accepted. The options button (3 dots in top-right corner) does contain the Bulk Change button on Jira Cloud. Click on the ellipsis at the top right. If you've already registered, sign in. Start a discussion Share a use case, discuss your favorite features, or get input from the communityClick on its name in the Backlog. I am working with a few folks on moving their issues over from NextGen to Classic Projects. If you aren't seeing an option for Bulk Change - check the global permissions for it. 1 from Windows 2003 to Windows 2012. Jira Software Cloud; JSWCLOUD-18112; Migrating Jira Next Gen Project to Classic needs to introduce drag and drop feature. The ability to clean them up in bulk after the import, as. When you integrate Aha! Roadmaps with a Jira team-managed project, Aha! Roadmaps will automatically detect the template type and create appropriate field. Startup the script and follow the prompt to correct the Epic Links in your next-gen Projects. I'm trying to migrate data from next-gen to classic and when exported . Jira Cloud; JRACLOUD-78620; Migration tool from company-managed (formerly classic) to team-managed (formerly next-gen) project and vice-versa. 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. Search in the marketplace. atlassian. Move them to the same project but the 'epic' type Jira Cloud here. Avoid passing through a proxy when importing your data, especially if your Jira instance. Requirements: 1. But they all seem to be disappeared. Just save the file with a text editor in a . If. move all issues associated with an epic from NG to the classic project. 2. If you've already registered, sign. click on Create new classic project like in the picture below. On your Jira dashboard, click Create project. I am unable to provide any comparison. Create . Have logged time show up in the Worklogs. Migrate between next-gen and classic projects. You're on your way to the next level! Join the Kudos program to earn points and save your progress. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-defined chunks. Dec 06, 2018. Please kindly assist in. Thank you. I'm trying to use the REST API to search all issues in the Project that have ever been a different issue type. Project admins of a next-gen project can now access email notifications control via the Project Settings. Migrate between next-gen and classic projects . You will need to set them up again in your cloud instance after migrating your projects. For example: Epic links and issue links: Any issue links in your classic project will not exist in your. and up. Jira Work Management ; Compass ; Jira Align ; Confluence ; Trello ; Atlas Bitbucket ; See all. 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 . Copied the home directory to the AWS EC2 instance and the rest is just making the connections as you said. Next-gen projects are independent of other next-gen and classic projects, so the custom fields, workflows, permissions are not shared between them. Browse templates across the Jira products you own, with additional information to assist you in finding the template that best fits the way your team works. I'm experiencing the same issues. Is there a step by step on how to do that? Thanks, Gui. 1. The new approach to configur e email notifications for next-gen projects is simple, easy to navigate, and gives complete control of email notifications to project admins. From the doc you've linked: Active sprints: Sprints in progress in your classic project won't move to your next-gen project. The Fix Version is actually the built-in one. atlassian. py extension and download the required " requests " module as its written in python. One of the last steps of the migration is the import of users and groups. Create . It has a very clear overview on things to consider during that migration - both ways. Since Deep Clone offers also some more advanced cloning options you might not have to update data after cloning. On the next screen, select Import your data, and select the file with your data backup. Bulk transition the stories with the transition you created in step 2. Converting from Next-Gen back to Classic. 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). Our development teams are interested in hearing your feedback - the bottom of the sidebar in next-gen projects provides a quick way to send feedback right from Jira: Fill out the form and hit. This change impacts all current and newly created next-gen projects. e. Moving epics and issues manually from UI is cumbursome and time consuming. 4. Next-gen projects support neat, linear workflows at. It means that the site was already wiped. Hello @JP Tetrault & @Stuart Capel - London ,. Hello, You should have read the guide for migrating next-gen to classic. Jira Service Management ;Where is the best place to find a comparison of Jira Next gen models with the Roadmap versus Jira Classic?The goal would be if there are some features added to next-gen in the future Jira users would be able to move their issues and project state to the next-gen project type. One of the differences in comparison with the classic project type is that customer permissions should be managed only on the Customers tab, leaving the internal project. Click on its name in the Backlog. Now, migrate all the tickets of the next-gen project to that classic project. select the issues in the bulk change operation: 2. Nov 26, 2021. Jira next-generation projects. 2. As I understand you want to migrate your application server but database will be the same. You may migrate to Slack V2 Next Generation by using the instructions below. You would need to migrate between next-gen and classic projects first and then flip back to next gen projects after the migration. Atlassian Team. - Add the statuses of your next-gen issues to the columns of your board. Ask the community . . Classic projects are now named company-managed projects. Jira Core help; Keyboard Shortcuts; About Jira; Jira Credits; Log In. Ask a question Get answers to your question from experts in the community. For details see: Create edit and delete Next-Gen service desk. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. What I am wondering is if there Next-gen projects and classic projects are technically quite different. 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. You can migrate application server and start application. In a cloud-to-cloud migration, data is copied from one cloud site to another. If you have been using Jira Cloud you will more than likely have noticed the new next-gen Projects that are now available. I have been charged with setting up a project for a project for a fairly simple team migrating from Rally to Jira. I can see that you created a ticket with our support and they are already helping you with this request. Project settings -> Issue types > (select the correct issue type) List of fields is now available and you can add. 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. Auto-suggest helps you quickly narrow down your search results by. Before I migrate our issues over to the new classic board I wanted to test it out before moving my team over. First, developers can now create issue fields (aka custom fields) for next-gen projects. Issue Fields in Next-gen Jira Cloud. 5 - 7+ seconds to just open a ticket from the board. Is there a way to go back to classic. If you are in a situation where you need to migrate projects with thousands of issues, it is physically not possible. Hello. 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. Script to migrate a Jira Classic project to Next generation project - File Finder · maknahar/jira-classic-to-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. If you need a customized workflow, Classic projects are where you want to be for now. There is no workflow assigned to the project (they might enhance this) You can add a new status directly on your board. I need to be able to have the classic projects to Next Gen so I have access to those custom fields. If I understood correctly, the goal of Next Gen was to simplify JIRA, namely: how workflows, custom fields, custom screens, permissions, etc. It would look something like this: 1. 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. Log In. abc. 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. Your project’s board displays your team’s work as cards you can move between columns. Export a project from one JIRA instance and import it into another. Overall it sounds like there could have been an issue installing. . Ask the community . Jira does not support CSV import facility in next gen project. Can I. If you're upgrading both Jira Core and Software and Jira Service Desk during the migration process, upgrade Jira Core or Software only. Ask the community . Create . Search for jobs related to Jira migrate classic project to next gen or hire on the world's largest freelancing marketplace with 22m+ jobs. Jira server products and Jira Data Center don't support these. Keep in mind some advanced configuration. Start a discussion Share a use case, discuss your favorite features, or get input from the community. Either Scrum or Kanban will already be selected. 4. Used it to move some Next-Gen issues just now to verify. Skip to content Toggle navigation. But since Deep Clone creates clones, the original issues remain unchanged in the. 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. Now, migrate all the tickets of the next-gen project to that classic project. You can find instructions on this in the documentation. 1) Use the project export/import feature. Add the "Time tracking" field to an Issue Type in Next-gen Project settings. Thank you for mentioning Deep Clone for Jira, @Ismael Jimoh . Classic has the option to setup automation with Automation and Project Automation, but Next-gen only has the option for Automation. Click on the issue tab, the regular blue Create button appears at the top from which i create a new issue. I would suggest that Next Gen is simply badly named. The Roadmaps feature is currently only available in Next-Gen projects. Create . Browse templates across the Jira products you own, with additional information to assist you in finding the template that best fits the way your team works. Hello, Is it possible to change/convert next-gen Jira project to classic? Products Groups Learning . About Jira; Jira Credits; Log In. XML Word Printable. This Project has 5000+ Issues and I need to migrate it to our Production instance. I am working with a few folks on moving their issues over from NextGen to Classic Projects. One of our teams/projects is migrating over to Next Gen. 5. So, the first. With that said, I really understand that next-gen is very limited in features and this type of project was created for small teams, that’s why many features of classic projects were not added. Select a destination project and issue type, and hit Next. On the other side… we now must migrate to Company-managed projects (former Classic) as your progress on Next-Gen roadmap did not move forward as much when it comes to our needs. Then, delete your next-gen projects. Products Groups . . I have created the custom fields same as in Next Gen projects. Services. It would be my expectation that all comments are migrated from the ticket in Classic Jira to Next. 1. choose the project you want from the selector screen. 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 a batch of tasks I want to make subtasks under another task. Is there a way to automatically pop. But as covered in the blog: There is no public REST API available to create project-scoped entities. Create . However, I don't have experience with Classic Software projects and am afraid of possible disadvantages I'm not seeing. I went into my Next-Gen project settings -> Features. Create a classic project and set up a workflow in that project. Will our TM4J test cases associated with that project move with the rest of the records? If yes, will those test records/customized fields be impacted by this transfer?. Our Legacy Slack V2 integration has reached end of life. How to config Multiple Active Sprint work on JIRA Next-Gen. 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". It will involve creating a new Classic project and bulk moving all of your issues into it. Find and fix vulnerabilities Codespaces. Host and manage packages Security. select the issues in the bulk change operation: 2. Next-gen projects and classic projects are technically quite different. We have configured a Jira Next Gen project. Can I. As of now, migration of next gen projects between cloud sites is not yet supported 1-1. i would like to switch back to classic. Hey all, I set up a project a little while ago and realized that the next gen software project by JIRA is really great: Products Groups . To see more videos like this, visit the Community Training Library here . I have recently set up a next gen project and cannot make use of JIRA portfolio or any reports - please can you advise if i can migrate back to the. Are there any future plans to allow the migration to the next-gen board? We plan on closely tracking the added features listed on the next-gen roadmap and seeing if the solution fits our use case. I am trying to bulk move issues from my classic project to a next-gen project. Products Groups Learning . 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. 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. Hi, Colin. I'd like to export all current stories from current next gen project into a newly created classic board. There aren't really disadvantages to Classic projects at the moment. Jira Service Management ; Jira Work Management ; Compass ; Jira Align ; Confluence ; Trello ; Atlas ; Bitbucket ; See. 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. However, having spent some time investigating the Next Gen versions, I believe the Next Gen workflows offer more of what I am looking for at the moment. Ask the community . I'll have to migrate bugs from a classic project until this is added. Issues that were in the active sprint in your classic project will be in the backlog of your next-gen project. It's the official Atlassian Supported tool for these types of tasks. 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. Currently our Instance has 300+ projects and lots of valuable data including 300K issues. cancel. XML Word Printable. 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. 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. Our new list view, available in both next-gen and classic project templates, helps you get an overview of all the issues in your project in a simple table that can be easily filtered, sorted, and exported. repeat for each epic. Ask a question Get answers to your question from experts in the community. Jira Work Management ; Compass ; Jira AlignIn classic projects, this does not work so. 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. What Jira refers to as "templates", are the default project configurations that you can select from when you create a project (eg: Scrum, Kanban, Bug Tracking, Project Management, next-gen, etc) and. It looks like many of my tasks/issues did not migrate over. Hi, Am trying to migrate jira cloud to on-prem. 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.