Can We Require A Context For Any Created Custom Field?

[Michael Spoonauer]

I absolutely understand that it should be the goal of any organization to keep the number of custom fields that are created in general as low as possible, due to both performance considerations and to the value gained in custom field reuse / standardization.

However, for organizations that do not (yet) have Jira Admins that enforce the reuse of custom fields, is there any way to force that any newly created custom field always be assigned a project-specific context?

This would never stop a custom field from being reused.  You simply add another context.

But this would stop the sprawl of custom fields into field configurations across all projects in a Jira instance, and would lessen the probability that, with the creation of each new custom field, we necessarily make Jira slower for everyone.

[Nic Brough -Adaptavist- · Accepted solution]

No, there's no way to do this.  If someone can add a custom field, they can set any context and it defaults to global.

[Michael Spoonauer]

Thanks, Nic.

I created https://jira.atlassian.com/browse/JRASERVER-71297 as a feature request.

Thanks,
Mike