You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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")
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events