Any way to define a field configuration additively instead of having to hide all?

[Nick Fox]

Field configurations appear to begin with including all fields defined for your Jira installation. For my organization, this involves sifting through literally 100+ fields I have to manually hide to create any new configuration. Is there a way to start from All Hidden?

Why are all fields associated with any project in the first place? Unless I'm understanding it incorrectly, it seems like a lot of excess DB overhead to have them read and merely hidden from a view.

[Nick Fox · Accepted solution]

I have found the Scriptrunner script provided in this comment enables the functionality I was hoping for:

https://community.atlassian.com/t5/Jira-questions/ScriptRunner-Groovy-getting-fields-and-adding-them-to-store-into/qaq-p/745252#M242461

You provide the project key and field names you want to enable and it hides all other non-system fields in the configuration.