I'm looking for best practices in regard to customization of issue types.
In an enterprise setup with 100 teams that are using the same Jira instance and want to use custom workflows and fields, how show I handle the customization requests?
That's annoying for the end-user - presenting them with fields they don't need on an issue type is not friendly, and a good admin will keep the fields as simple and clear as possible to save them time!
On a technical level, many fields is one of the ways you can cause issues. Performance is quite a complex thing in Jira, but each and every different field causes overhead you would want to avoid if you can. But you can minimise that by limiting the context of fields. (On this one the short answer is "a field that only exists in project X on issuetype Y is more performant than a global field")
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Become an effective Jira admin
Manage global settings and shared configurations called schemes to achieve goals more quickly.
Streamline Jira administration with effective governance
Improve how you administer and maintain Jira and minimize clutter for users and administrators.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.