Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-7360

Unification of built-in and custom fields

This issue is archived. You can view it, but you can't modify it. Learn more



    • Bug
    • Resolution: Fixed
    • Medium
    • 4.1
    • None
    • None


      When we introduced custom fields, they were bolted onto the side of JIRA, introducing needless extra complexity an inconsistency in the admin UI.

      Say I wish to edit a field description; the process is different depending on whether a field is 'built-in' or 'custom':

      • For custom fields, click Custom Fields -> Edit (on the relevant field)
      • For built-in fields, click Field Configurations -> Default Field Configuration -> Edit (on the relevant field)

      Or say I wish to edit the options in the 'Priorities' field. If this were a custom field, I'd just click 'Configure'. Instead I have to go to Issue Settings -> Priorities.

      Users shouldn't have to care whether a field is 'custom' or built-in. It is an implementation detail, not something relevant to the user's mental data model of a JIRA issue.

      To fix this, we should have a single config page, called 'Fields', listing built-in and 'custom' fields. Each field would have an 'Edit' link (for changing name/description) and a 'Configure' link (for changing values). Built-in fields (those always required) might be listed at the top. We can then get rid of the whole 'Issue Settings' admin menu, since Issue Types, Priorities, Resolutions and Statuses will be configurable from this page like any other field.


        Issue Links



              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              mandreacchio Michael Andreacchio