We've heard that multi-line text custom fields adversely affect JIRA performance.
If we always configure these custom fields to only be applied to a single project will that help? We have a couple projects where are customers are asking for multiple multi-line text custom fields and we are weighing these requests against our JIRA performance.
Any advice welcome.
Yes, it will help a little bit because JIRA is structured in a way that checks if there is anything to read first. When the field doesn't even exist for the project (or issue type), it can stop work at that point, rather than asking for the data to be retreived (and having to process either "no data" or "here's some data"). There's also something about the specific way it is stored in indexing which helps the speed when fields are project-specific, but I'm not going to pretend I understood the rest of the conversation I had about that one.
It will be faster, but you may struggle to measure it unless you're on a big, heavily loaded, JIRA.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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