the # of custom fields alone is the biggest concert. See the following quote from the Scaling JIRA doc:
"the number of custom fields has highest impact on the actions that request or process custom issue details, i.e view all issues, search with JQL, create issue, edit issue"
Recommended practice is to use less fields but utilize multiple field contexts. For example:
If you have field called Teams and it is single select with different values for different projects, then instead of creating two separate global fields with different options, you can create one with two separate field contexts.
Hope this helps. Let me know if you need more info.
There are custom field types that have more effect on performance than others.
Q5. Which custom fields have the most performance impact?
A5: Free text custom fields are probably the biggest performance eaters. The smallest performance eaters would be the multi-select custom field.
Q9. Are the number of issues the largest impact on JIRA’s performance?
A9: The number of issues is not actually what has the largest impact on performance in JIRA, especially since 5.1. The amount of custom fields would be an example of something that has a larger effect on performance. For additional details please refer to our scaling JIRA documentation.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs