, Classic project: 1. Jira Service Management ; Jira Work Management ; Compass ;Jira; Questions; Classic software projects can be seen by people added to next-gen software projects;. 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 Submit! Thanks Chris. In organisations where consistency in the way projects are carried out is important, whether that be to improve efficiency, increase transparency for product owners and stakeholders, or any other reason, classic Jira. We’d like. There is a feature suggesting a migration tool for classic to next-gen: Migration tool from. 3. We’ll keep up with the updates to see if Atlassian decides to extend the functionality of next. Now I am moving 50 Issues (just selecting the first 50 which is a. We've listened to your feedback, and I'm pleased to announce that we shipped a new feature we call user-based swimlanes. My frustrations with JIRA are the cumbersome nature of it for small startups, Classic vs. This transition would be a change of type for an already existing project. Creating a Jira Next Gen project for each initiative, did not allow me to show all in one view, without going through unnecessary hoops. For Creating Next-gen project you have to have global permission - "create next-gen projects permission" Please confirm if the details are correct and then we can troubelshoot. Workflow can be defined to each issue. 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. Ask a question Get answers to your question from experts in the community. The following tips will help you to create a useful Jira. Commits are selected by issue key. . Ask the community . Select Projects. Shane Feb 10, 2020. A csv import will update existing issues if a column with issue keys is mapped to issuekey field. There aren't really disadvantages to Classic projects at the moment. Teams working in a kanban management framework focus on reducing the time it takes a project—or a user story within a project—to move from start to finish. Overall it sounds like there could have been an issue installing. Click “ Project Settings “→ “ Development tools ” (bottom left) 2. Like Be the first to like this . If I create a filter using this query: project in (pfw, ppiw) This returns all of the tickets in those projects. Hi Atlassian Community, I work on the Jira Software product team and I am happy to share that we have just added support for third-parties, such as GitHub and GitLab in Jira Software Cloud’s Code in Jira. for now I use a manual workaround: I bring the Epic name in as a label then filter. With this Jira Cloud integration, you will: No longer need a token or to be an admin to set up this integration. Click on the Disable Zephyr for Jira in Project XXX button. ”. . It is high time to talk to your Jira administrator and design together your workflows, status types and project configuration. as far as I know, you can add an issue as child of an epic only if the issue belongs to the same project of the epic. For this scenarios, Jira states: Users should query on next-gen epics using the parent =. TMP = next-gen. In the meantime, until the feature is added by Atlassian, you might want to use a third-party app that helps with time tracking in both Classic and Next-Gen projects. Welcome to the Atlassian community. The Roadmaps feature is currently only available in Next-Gen projects. Ask the community . I also did not find a way to configure these. I need to be able to have the classic projects to Next Gen so I have access to those custom fields. If you'd like to create Epics and Stories, you'd need to add them manually to a non-software project. Dec 1, 2022. Recently, Jira Service Management introduced a new type of project - Next-Gen project. For example if you had a request type called 'Request time off' you can hide the summary field on the portal, and preset the summary text to 'Request for time off' or whatever. Like in Classic projects, I am okay if they are visible in the Issues Navigator tab via filters. 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. If cloning from a ne. Would it possible to use Next-Gen Jira roadmap feature in classic Jira Software version? I would like to visualize dependency as in Next-Gen Jira version for Roadmap feature in classic Jira software version. Then, in the top-right corner, select more (three-dot sign) and Bulk change all. We have a feature request suggesting the implementation of this ability: Add "Board settings" to next-gen projects. The system will open the Bulk Operation wizard. you can't "migrate" precisely in that there is no 'button' to migrate. We have Jira Classic. Kanban is a Japanese word meaning visual signal. I've read that the tickets in the "Done" column is archived after 14 days, but my preference is that they are remove together with the corresponding version as I release that version, or the "Done" column early get very cluttered. In Classic, on the left hand gray bar under the project's name is the board's name. For example, for bug fixing tasks using Kanban and for the new feature type projects to use Scrum. would be managed in a much more robust end simplified way, without losing the key functionality. Keep a look out for further updates. View a list of versions, their status (released, archived, unreleased) and the progress of that version via the releases page. Jira Software; Questions; Turn off next-gen; Turn off next-gen . Maxime Koitsalu Dec 06, 2018. - Back to your board > Project Settings > Columns. By default, you must order your board filter by Rank in order to allow the manual sort of issues in a Kanban board. But the next-gen docs about sprints don't mention this. Hey David, John from Automation for Jira here. If you're in a scrum project, you'll need to create and start a sprint to begin tracking work. On the Select destination projects and issue types screen, select where issues from your old project will go. With this access level, Jira gives anyone who logs into your Jira site the Member role in your project. Products Groups . Creating a classic project is different from creating a next-gen project: you need to have the "Administer Jira" global permission to be able to create classic projects. This product roadmap encompasses where our customers tell us they are going next, and the features we need to build to help them get there. Issues are the heart of Jira. Hi, I miss the point of these features since they already exist in classic projects. See below and compare similarities. - Add your Next-gen issues to be returned in the board filter. 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. 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". . Your project’s board displays your team’s work as cards you can move between columns. Hello, Is it possible to change/convert next-gen Jira project to classic? Products Groups Learning . The introduction of next-gen projects led to the undesirable side effect of developers not being able to create project configuration entities such as the ones referenced above. Is there anything I need to Atlassian Community logo1 answer. then you can use the connect app API for customfield options. Please be informed that, on next gen boards on Jira Software Cloud, issues which are moved to status 'DONE' are no longer visible on the Kanban board after 14 days. 4) Convert a Project to Next-Gen. :-It depends if your project is NextGen or Classic. A vast majority of agile teams utilize the scrum and kanban templates, and within these. Create and assign an issue to a particular fix version. Software development, made easy Jira Software's team-managed projects combine simplicity and. you may see some other posts I have raised concerning the Epic problem. Request type fields are based on their associated issue type’s fields. Click on the lock icon on the top right of the Issue Type screen. - Back to your board > Project Settings > Columns. Start a discussion Share a use case, discuss your favorite features, or get input from the community. Rising Star. Step 1: Prepare an Excel file. Auto-suggest helps you quickly narrow down your search results by. Migrate between next-gen and classic projects. {"payload":{"feedbackUrl":". They're perfect for teams that want to quickly jump in and get started. The system will open the Bulk Operation wizard. When I create a new project, I can only choose from the following next-gen templates. The fundamental concepts remain the same, but the UIs are different, so it's important to clarify that the screenshots in this article are from Jira Next-Gen, rather than classic Jira. 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. The functionality remains the same and will continue to be ideal for independent. For classic, the epic links are created from the 'Epic Link' field OR by dragging an issue card in the backlog on to an Epic in the 'Epics panel' (left sidebar): For Next-Gen projects, you are able to add Epic links (parents) from the dropdowns you are looking at AND from the breadcrumbs: Like. @Lily Is there a reason for not clearing the "Done" column of its tickets whenever you release the version they belong to, or is this feature yet to be developed?. The columns on your board represent the status of these tasks. 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. 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. Hi @Michael Galper To allow users to create Classic projects you might have to add them to Administer Jira global permissions (which is a dangerous thing to do). Products Groups Learning . This document should help you out - migrate-from-an-next-gen-project-to-a-classic-projectNext-gen projects were created to be more simple, so currently it's not possible to create a filter for Burnup and Velocity reports. . There are currently no REST API endpoints for adding custom fields to Team Managed (NextGen) projects. Thanks for the patience guys, any requests/comments for Estimation related functionality should be made here. 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. It's native. Bulk transition the stories with the transition you created in step 2. Click the Project filter button and choose the project you want to migrate from. If you open a classic project you should see the link in the issue next to the Status field. COMPLETION. However, there is also a symbolic version, called latest, which resolves to the latest version supported by the given Jira Software Cloud instance. The graph will look different if you are using Issue Count as your Estimation Statistic (rather than Story Points, as shown in the screenshot above). From the sidebar, select the issue type you want to edit. Ask the community. 1. ”. cancel. It gives you the streamlined user-friendliness of Scrum and Kanban boards, along with the added functionality of enterprise solutions. Jira component is an issue-grouping technique, used for breaking all project’s issue pull into smaller parts. When doing Scrum of Scrums or attempting to link between Next Gen project management ticketing and Classic development team tickets we are hitting. Right click here to open this video in a new browser tab for more viewing options. Opening the roadmap tool, only the NEXT GEN epics are available to be dropped into the roadmap. However, you can move all issues from the classic project to the next-gen. Connect your GitLab. 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. Manage requirements efficiently to reduce your development costs and speed time to market. IBM Rational DOORS Next Generation (DNG) – formerly Rational Requirements Composer – is a repository for storing the requirements to which a software program is developed. GitLab. Click on “Update Work flow” in the top right corner and select “Bug” from the dropdown menu. Our solutions use the power of AI to improve the quality of engineering requirements as you write them and help. ) the "Closed" status to Jira's global namespace, which adds an unworkable amount of noise to querying in Classic (and also provides no end of trouble for many of your third-party marketplace vendors in the automation and reporting space). Next-Generation Jira Projects is an Atlassian Cloud feature designed to allow teams to collaborate on projects with an emphasis on being able to quickly tailor their board, fields, and other features without requiring a Jira Admin to make the changes. This name change reflects the main difference between both types — Who is responsible for administering the project. 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. However there is no option to import the comments. The various requirements must be. This allows teams to quickly learn, adapt and change the way. They are built with the most important features of Classic Jira incorporated. . It's not possible to prevent administrators to create classic projects. Therefore, most of the features and settings in the classic version are. We are trying to author a requirements document and create the epics and user stories as part of that authoring. We have some feature requests related to filters for next-gen, but nothing related to reports: - Roadmap Epic filter in next-gen projects. To create a link between your Git commit and a Jira issue, developers must include the issue key into the commit comment. If you've already registered, sign in. We're in the very early stages of testing to see if Jira Service Management is a fit with our organization. Default language in Classic can be set / changed anytime, but Next-gen has to be setup upon creation. But I cannot find a way to get "Resolution" to appear at all in my next-gen software 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. Clockwork allows tracking time automatically, through Start/Stop Timer button as well as through the "Log Work" button that pops up a. They mean to simplify the project configuration experience for. Jira Service Management. 3. It is a template used when creating a project. Currently in Jira Server you can authenticate by using OAuth, Basic, or Cookie-based authentication, depending on what you're trying to do. If you've already registered, sign in. but just to let you know that when we migrate from a next-gen to classic, it's not possible to keep the same project key and also the issue key will change. py extension and download the required " requests " module as its written in python. 99/Month - Training's at 🔔SUBSCRIBE to. Otherwise. Change your template—if needed—by clicking the Change template button. 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). Setup and maintained by Jira admins, company-managed projects will remain the best choice for teams who want to work with other teams across many projects in a standard way, such as sharing a workflow. When I go to the backlog of the board, only NEXT GEN project Epics are shown in the backlog/stacked view, all CURRENT GEN project epics are shown in the epics panel. The. How can I migrate from next-gen project to classic scrum project. Answer accepted. How can I convert it to classical type Jira Project ? This year Atlassian renamed the project types to use more meaningful nomenclature. 5. No board settings / or the "+" symbol to add a new column in Jira next gen project: Board settings available and the "+" button to add new columns in Jira classic project: Any ideas or solutions to solve this issue? Thanks in advance Katja For example, for bug fixing tasks using Kanban and for the new feature type projects to use Scrum. You must be a registered user to add a comment. In team-managed projects, creating a new status means creating a new column on your board. 6. 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. You'll see this screen:Linking git commits to Jira issues. Include up to the last 10 comments directly in the email. 5. The prompt wouldn’t show up if you are already moving all the child issues along with their respective epics at the same time. Share. Answer accepted. There is a subsequent body of work that we are just about to start that will give: Jakub. The option to show "Days in Column" is currently only available for Classic projects, since the Board settings were not released for next-gen yet. They have the permission to create next-gen projects but they miss the 'Browse Projects' permission. the problem is that Next-gen does not currently handle Epics in the proper way like Classic projects. Can you please give the detailed differentiation in between these two types. Ask the community . The release of next-gen also came a year after the. You can create a workflow rule not to allow stories to move from one swimlane to the next. Click on Use Template. I have been charged with setting up a project for a project for a fairly simple team migrating from Rally to Jira. thanks. As for an idea portal, the only thing I can think of is to create a new next-gen project and add employees and customers as members and use created tasks as ideas and/or suggestions. Jira next-generation projects. Steven Paterson Nov 18, 2020. In the end, we have given up on Next Gen and moved back to classic Jira. I am fully aware that sub-tasks are not yet. In next-gen projects, the only way currently to see sub-tasks on a board is to use the group by function. The process is a bit tedious and depends on the details of your starting point w/ the Classic project. Next-gen projects use their own workflows that are different from classic projects, and the view does not include the "view workflow" link. - Add the statuses of your next-gen issues to the columns of your board. We are porting projects from next-gen to classic as we migrate from Jira Cloud to Jira Server and it is not easy. I would like to make sure the issues and the issue suffix are not deleted when I dele. We hear d the name “next-gen” can be confusing, so we’re renaming next-gen and classic in a way that is much more clear and descriptive of the projec t type: Next-gen projects will be named team-managed projects. Note that I have an epic issue type mapped in classic project but still the epic in nextgen gets migrated to a story in classic. In Cloud Free plan, anyone with a Jira Software license will be an administrator for all Software and Core projects. By following the import wizard till. In the meantime, we do support some aspects of NextGen projects, and we will support them fully once. Nearly a year ago we launched the next-gen template, where we reimagined parts of Jira Software Cloud’s core functionality. Jira really needs multi-level hierarchy similar to what Structure provides. Create a new company-managed project to receive your existing team-managed project requests Jira Cloud has introduced a new class of projects — next-gen projects. I want to enable the testers to create next-gen projects. JIRA provides a lot of support in1. There is an option to create a project with a shared configuration that copies the settings from a project to another, but it. As for column mappings in Next-Gen t he last. 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. The integration will then continue to use the level of API permissions available to. Create and assign an issue to a particular fix version. Dec 07, 2018. ) four Next Gen projects introduces four different versions of (e. 5. We have two types of service projects: company-managed and team-managed. - Add the statuses of your next-gen issues to the columns of your board. Secondly, there is a toggle for 'the new jira view'. As mentioned by Daniel Eads cloning between classic to next-gen projects is possible with our cloud app Deep Clone for Jira. - Add the statuses of your next-gen issues to the columns of your board. You can also click the “See all Done issues” link in your board’s DONE column. I am migrating from a Next-Gen to a Classic project. They also ensure that smaller teams in the eco-system can. The timeline view is valuable for creating and planning long-term projects. Currently, there is no way to convert next-gen to classic projects. We are rapidly shipping new, innovative features to make using Jira Software easier while increasing its power. Configuring columns. Then, delete your next-gen projects. My name is Bryan Lim and I'm a Product Manager working on Jira Software Next-gen. Select Move Issues and hit Next. Depending on the. We recommend you to work with a classic Jira project, Software type. One issue in moving the epics and tasks from next-gen to classic is that they lose their relationship. Issues are the heart of Jira. 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. Editing this associated screen may impact other request types with the same screen. I am trying to bulk move issues from my classic project to a next-gen project. Configure the fix version field to appear on your next-gen issue types. g. they are just different, a trade off to make Jira more accessible to users that don't have an experienced or certified Jira administrator. 3. Ask the community . Free edition of Jira Software. Jira is built around the Agile development process. 5. The Next Gen projects are the latest project types in Jira Software. Portfolio for Jira next-gen support ; Also the incompatibility is only at the project level, instance wide you can have a mix of both nex-gen and classic projects, with the classic projects usable by Portfolio with full functionality and next-gen with limited functionality. Go back to the Manage your apps page, click the Zendesk. Subtask issue types are different from regular issue types. Yes, unfortunately, NextGen have broken a number of APIs that Automation for Jira (and other apps) depend on. Haven't tried it in the past. Next-gen projects are independent of other next-gen and classic projects, so the custom fields, workflows, permissions are not shared between them. Get all my courses for USD 5. Hello @Michael Buechele. Essentially, custom fields for Company Managed projects belong to the whole Jira instance and get allocated to the projects via configuration schemes, which give them a context per. They are built with the most important features of Classic Jira incorporated. I know it is in the project settings in classic jira but I don't see anything in the next. Dump next-gen and make classic project to incorporate team members. To enable approvals on your instance, head to Project settings > Request types, and click the Edit workflow button at. If you go into your system and to the "back-up" management section it will actually list all of your next-gen projects. Now I need to know how to migrate back to classic project to get all those things back. For Jira server or Jira Cloud using classic projects, the editor in use for both descriptions and comments is the same and won't allow this in-line code formatting on the same line. . I understand your point. Jun 24, 2021. The core functionality of these project types are the same, but there are key differences you should know in order to decide what’s right for your team. Cheers, SyauqiThe major difference between classic and next-gen is the approach they take to project configuration and customisation. If you're using Jira next-gen projects, support for JQL behaves differently compared to classic Jira projects. Select either Classic project or Try a next-gen project. The Story Point Estimate field seems to migrate, but is NOT used in the rolloup of points for a sprint. We are porting projects from next-gen to classic as we migrate from Jira Cloud to Jira Server and it is not easy. specific steps would be: - Navigate to your classic board > Click on the three dots Icon > Board settings > Edit filter query. You can't convert a project from Next-Gen to Classic unfortunately. ) the "Closed" status to Jira's global namespace, which adds an unworkable amount of noise to querying in Classic (and also provides no end of trouble for many of your third-party marketplace vendors in the automation and reporting space). Email handlers and the email channel for service desk projects are not defined as "classic" or "next gen", your upgrade will not have changed anything. You can create a classic project and bulk move all issues from NG to the classic one. You can add your next-gen project to any of the categories (pre-defined by your Jira admin) from the Details page in Project settings. Select the issue type you want to edit. Ask a question Get answers to your question from experts in the community. It's Dark Mode. Choose Find new apps and search for Jira Cloud Migration Assistant. Choose Install. . Click on the magnifying glass, scroll to the bottom and in the Advanced search dropdown select projects. In this article, I want to talk about JIRA next-gen (and hence they refer to their older version as classic :) ). Create . To create a new project (see Figure 1 for field details): Go to Projects menu on Projects page in Jira . Introducing dependency & progress for roadmaps in Jira Software Cloud. Are you on the right help page?. I already tried to move the issues directly from next-gen to Classic-Jira project. To top it off, their Portfolio/Plans/Roadmap software has been handled in the same confusing way as. Select the start of your transition path in the From status dropdown. For this, we’re excited to share we’re bringing the next-gen roadmap directly into classic projects. Since the dates you refer to were (most likely) stored in custom fields in your next-gen project, these were lost on transfer. Hi , My query is , is it possible to get S curve in Jira dashboard with any plugin help ? Can you refer any link or documentation? Do we have any similar type of gadget in dashboard for that ? (Plotting Date fields Vs status)Here is a list of gadgets that can be used to build a powerful dashboard in Jira for tracking a Kanban project in an effective way. Clockwork Automated Timesheets allows tracking time with the manual Start/Stop timer button or automatically when an issue is transitioned between statuses. 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 that. Then I can create a new Scrum Board based on this filter, and those tickets. It allows you to customize the hierarchy between issue. A few days ago we released an update that fixed some issues with next-gen. In that stage instance, I have created a Classic Project with the same fields as the NextGen Project and tested a few (3) Issues. Then select a Company-managed project. Your software or mobile app can be tracked with Jira,. Feel free to ask any questions about. Currently trying to utilize the Next-gen Jira, using the "Move" functionality to take a ticket from a Classic Jira project when attempting this it asked map field etc. specific steps would be: - Navigate to your classic board > Click on the three dots Icon > Board settings > Edit filter query. If you haven't already taken a look, I would encourage you to read through the roadmap for next-gen projects in Jira. To see more videos like this, visit the Community Training Library here . Mar 12, 2019. How do I switch this back? It is affecting other projects we have and our. . One of our teams/projects is migrating over to Next Gen. But for projects that need flexibility, Next-gen simply is not ready. If you click on the name of the board a drop-down menu will appear to show you the names of other boards within the project. How can I convert next-gen project to non-next gen/Classic? I created new project as next gen, but now I cannot use workflows or schemes, or. Jira Software’s free plans give you access to almost every feature for up to 10 users with no strings attached, along with 1,000+ apps and integrations. Next-up we’re adding support for 3rd parties (GitHub, GitLab etc. You can read more about next-gen here. You must be a registered user to add a comment. There's an option to move issues from next-. Team managed is where you will find the group by feature in the scrum board. The fundamental concepts remain the same, but the UIs are different, so it's important to clarify that the screenshots in this article are from Jira Next-Gen, rather than classic Jira. When it comes to configuring next-gen project, it was a page, yes "a" page and few. For example, if you wanted. That's the infrastructure behind JIRA. TMP = next-gen. The names were updated from “Next-gen” projects to “Team-managed” projects and “Classic” projects to “Company-managed. If you want to change the preselected template, click Change template, and select the appropriate template for your. So you don't migrate "boards" but rather you migrate the issues from a Classic project to a Next-gen project. Edit Epic issues fields – all standard Jira fields and created standard custom fields can be edited in multiple ways. When you create a next-gen project you have the option to choose if it will be Open, Limited or Private. Select Add issue type. Playing around with Classic and NextGen side-by-side, I favor the allure of 80% of NextGen but must side with Classic for the sake of anyone else on the project. To track work items, move an issue from. Atlassian’s Jira tickets attempt to solve some of these problems by providing a place to collect information about a task and organizing work into doable chunks. Next-gen Projects By default the new next-gen projects come with all the latest, awesome stuff we have built all wrapped within a project. Hello! I will be migrating from Next Gen project to Classic and I have few custom fields made for my issues. We heard this frustration and have made updates to correct it. On August 7th @ 2:00pm PT (San Francisco) // 5:00 pm ET (New York), I'll be hosting a live Webinar & AMA to answer all your questions about next-gen projects in Jira. I'm having a permission issue where any user that has been added as a member of a next-gen project can see all classic software projects. However, as a workaround for now. I understand this method of view sub-tasks is undesirable in your use case. As it's independent projects, any issue types created outside the project, won't be available for next-gen. cancel. it saves time and makes it easy. I'm at a loss. This new configuration logic can be applied on a specific issue type within a specific project, across both the new next-gen projects and Classic projects. Solved: Need to switch a project from Next Gen to a Classic Project type. This is because on the Free plan it's not possible to manage project permissions. 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. With schemes, the general strategy for next-gen is that projects are independent of one another. Now I need to know how to migrate back to classic project to get all those things back. Hello @Ilian Jäger . Go through the wizard, choose the issues that you want to move and click Next. I have created the custom fields same as in Next Gen projects. In the sidebar, select Project Settings. Currently, adding (e. These issues do not operate like other issue types in next-gen boards in. If you want to LINK the data, keeping it separate and referencing as needed, you would need an OSLC connect tool - SodiusWillert's tool is excellent. In my template, I have issue types Epic and Task. 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. Next-Gen is not supported by most of the third-party macro vendors.