Is there a difference in performance between custom fields and built in jira fields?
I found in the documentation that built in fields aren't searchable through quicksearch. Are there any other features they lack?
The main difference is structural, although that's on two levels.
In the database, the system fields are stored mostly on the issue table and hence always exist, even when empty. Some, like versions and components, are stored by links in other tables. Custom fields are more simple in many ways - they're all stored in one place, with a set of lookup tables.
From the UI point of view, system fields are fixed in place - you get them on every issue, you can hide or ignore some of them, but you can't add them. You get a whole swathe of functionality around them, but it's mostly static and not changeable. Custom fields lack all that functionality, but you can add as many as you want.
Perf: Obviously, it really depends on the programmer(s). There are good programmers (and good CFs) and there are bad programmers (and bad CFs). That's not a question, IMNSHO.
Features: it really depends on the intended purpose, time (cost). Some choose to implement everything, some only a few things, etc.
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