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

Clearly mark custom fields that are coming from a 3rd party app/plugin or don't use a default custom field type

    XMLWordPrintable

Details

    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Problem

      It's difficult to differentiate between custom fields coming from a 3rd party app and fields coming from Jira. 

      The fields coming from a 3rd party app should be marked as such. This is especially important in the custom field optimizer where issue usage statistics can't be calculated for that field. Admins may think it's not in use and delete it. 

      Workaround

      Compare the custom field type against the default types. If it's not there, it must be coming from a 3rd-party app. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            adridi Arbi Dridi
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: