nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Map project fields to a field configuration for use in other projects

Mark Robinson_ttevtc

Maybe I'm coming at this in the wrong way, but I can't seem to figure out how to take the fields that I have mapped in one project and save them like a template for use in another.

I realize there are apps out there that help us to accomplish this but I'd like to set it up once and leave it alone.

I have a project, where I have gone into the various Issue Types and adjusted the fields and I want to use that same setup in other projects without having to manually go into each record type again.

I have looked into the field configuration section of the admin menu, and I can't seem to wrap my brain around how to get it to put together a config based on the project I have already adjusted.

Is this not what these configurations are for?

How can I get this template from project A on to project B?

Accepted answers

Andrew Kendris_io3cw5

Hello @Mark Robinson - are you trying to reference the configuration of a "Classic" project (i.e. company managed) or a "Next Gen" project (team managed)?

If it's a Company managed project, you can leverage the various aspect of that projects field configuration for future projects. To change your new project's configuration to match the one that meets your needs, you can go to the Project Settings section and then head to Summary to change its default Field Configurations and Screen Schemes to the other one.

Screen Shot 2021-03-30 at 7.26.08 PM.png Screen Shot 2021-03-30 at 7.24.56 PM.png

All comments

Andrew Kendris_io3cw5

Hello @Mark Robinson - are you trying to reference the configuration of a "Classic" project (i.e. company managed) or a "Next Gen" project (team managed)?

Screen Shot 2021-03-30 at 7.26.08 PM.png Screen Shot 2021-03-30 at 7.24.56 PM.png

Mark Robinson_ttevtc

Thanks for the reply @Andrew Kendris

The project where I have all of my fields configured is a "Next Gen" project. I would like to allow those fields to be used in other projects the same way that they show up in my project.

I was able to follow what you suggested to find the area where I would switch the scheme's, and when I use the 'Choose a scheme the same as an existing project' option my project A is not listed for use on project B.

Is that a limitation of the "Next Gen" project type?

Andrew Kendris_io3cw5

It appears your project B is a classic project. At this time, Next-gen projects (i.e. Team Managed) are independent of other next-gen and Classic projects (i.e. Company Managed), so the custom fields, workflows, permissions are not shared between them. Every time you want to stand up a new Team Managed project, you'll need to configure it from the ground up.

Currently, there is no option to clone or duplicate a Team Managed project. The option to create a project with a shared configuration that copies the settings from one project to another, is only available for Company Managed projects.

In your scenario, if you're looking to scale the configuration for project A (your Next Gen / Team Managed project), I would suggest building out the configuration in a Classic / Company Managed project.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

template

field-configuration