How to stop when a custom field is added, it gets added to all field configurations

[Brian Kohler]

When admin's of our JIRA instance adds custom fields to our instance as the use cases of using JIRA grows, one of the key observations is that the custom fields added are also added to ALL field configurations that are setup.  Meaning, those that spent the time at time of project creation to complete a field configuration for the custom fields that matter to the project, are expanded everytime someone adds a new custom field.  This impacts what shows up in Bulk, what data is stored (especially when default values are set on the new custom field) as well as what gets exported with "All".

I'm tired of ALWAYS going to reconfigure field configurations for the projects I administer when other members of the Admin team are expanding the use of the platform.

Is there a better way, or a setting to stop this behavior?

[Ollie Guan]

Hi @Brian Kohler,

I do not know whether similar permission control can be done through configuration and plugins. We have encountered similar problems before, and we adopted the following solution:

1. Limit the number of administrators
2. When an administrator creates a new field, it is associated with a specific IssueType and Project. Do not apply to the global.

[David Harkins]

Hi @Brian Kohler 

Have you been able to find a Solution to this?

Having the same issue here, multiple business departments in our instance and both Development ad Service Management.

Bulk Edit screens become longer and longer.  Users notice the fields and start using them because they are there. only to raise issues when they disappear. 

With near to 50 Field Configurations, it can become time consuming keeping them all in check.