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?
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?
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)
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 ?
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:
^ 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.
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.
Yeah, I did get an new config scheme / config.
I have an Default Scheme, and I have an newly created scheme(as done per instruction above). The newly created scheme has already been filled with the information of the Default Scheme, like it's linked somehow.
When making changes to this scheme, the schemes are also changed in the Default, like linking or un-linking an screen. See also the screenshot.
As you can see, 1 of the configurations is linked to an scheme. But when making an change in "Veldconfiguratie Project Ronit #2, these changes are also done in "Veldconfiguratie Project Ronit".
I hope this will help things to clarify.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events