Hi,
I’ve noted that it is not possible to remove a custom field from Field configurations. Our Field configurations display all custom fields ever created in our Jira. I can delete a field from a specific Field configuration if I disassociate it from the projects, however, it also deletes it from the Default field configuration, thereby impacting other projects. Similarly, any new field created in a specific Field configuration would appear in the Default field configuration and vice-versa.
I am not sure if this is the intended behaviour of Field configurations or if this is a result of poor initial set-up on our part.
If it is the intended behaviour, it would be good to understand why, and what the work around is. Currently there are 169 fields appearing in all the Field configurations.
Is it possible to create a Field configuration for a project without all the 169 fields (and associated project names) appearing?
HI @Vini Vincent ,
Field configuration is more for how a field should behaved. It usually would have mostly all fields available when they're created. In field configuration, for example, you can configure whether the field is optional or required or hidden. However, this does not impact what's actually displayed on your screens. You screens and screen schemes what shows up for each issue type in your project.
Hope the helps clarify things a bit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.