difference between built in and custom fields

Deleted user July 23, 2012

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?

2 answers

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 23, 2012

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.

0 votes
Radu Dumitriu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 23, 2012

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events