You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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")