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; } } }

jira field configurations linked

unknown

hi,

i created a new field configuration to adjust it so a project has a different field configuration instead of the default we use,

but when i change the new field configuration, the default one gets changed as wel??

how am i suppose to create a scheme to allow a project to not use default field configurations ?

so for instance if the default has a field application, and i create a new field configuration it copies the default values somehow? but i dont want application so i remove all the screens attached to application on the new scheme but the default also coppies those values?

Accepted answers

All comments

Ste Wright

Hi @[deleted]

The new scheme when first created might have similar options to the default one - especially if you created a copy but you can then modify it to suit your needs.

Your example though mentions removing a field from a screen for one project - this wouldn't be via a field configuration scheme - moreover, you'd need new screens / screen schemes / issue type screen schemes for that project with that field removed.

Could you provide a list of what you're trying to achieve and we can suggest the best solutions for each?

Ste

unknown

Hi Stephen Wright,

what i am trying to achieve is the following:

after creating a new fieldt configuration, i am able to change the new configuration fields but this still translated to the default configuration being changed

i currently have 41 projects with the same field configuration(DEFAULT). now we want a new jira cloud project which has certain fields required on creating a issue,

so i created a new project, with a new screen configuration, but when i create a new configuration it got all the default fields. now it seems strange to me that when you create a new configuration it is linked with the default(in terms of screens and such)

see default:

see new:

what i now wish to do is edit new screenconfiguration by making application for example, required but if i edit new screenconfiguration, the default gets edited as well ?

Ste Wright

Hi @[deleted]

A few things to answer here.

Every Field Configuration Scheme lists all available fields (whether on a Screen or not) and what Screens utilise these fields. The different field configuration is based on which projects the Config Scheme is applied to.

To apply a new Field Configuration to one project:

In Jira Admin Settings > Issues, go to Field Configurations
Create a new field configuration either by pressing Add in the upper-right or copying an existing configuration using Copy.
Make the necessary changes to this field configuration
Next, select the option Field Configuration Scheme from the left-hand menu
Press "Add Field Configuration Scheme" in the top-right and create it
Press Edit next to your new scheme
Change the Field Configuration in use on this scheme
You can add more field configurations per issue type using the relevant button in the upper-right corner if you need to
Now go to your Project's Settings and select Fields from the left-hand menu
Select Actions in the top-right and choose Use a Different Scheme
Change to your newly create Field Config Scheme

^ Make sure you've followed these steps otherwise your new Field Config Scheme will still be using the Field Config (a separate entity) which is default.

Let us know if this doesn't resolve the issue.

Ste

unknown

Hi Stephen,

I'm an colleque of Sebastiaan, and i'm now taking this over from him.

I did the things above, but the results are the same. When making an new Field Configuration, the fields are already filled in and when trying to change "schermen", the change is also processed in the other Field Configuration, Default Field Configuration.

Greetings Ronit

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud