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

Add Config Option To Require Every New Custom Field to Add a Context

XMLWordPrintable

    • 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.

      Would it be possible to expose a system configuration option that would enable an organization, if they choose, to enforce that any newly created custom field always be assigned a project-specific context and to automatically delete the global context?

      This would never stop a custom field from being reused.  You simply add another project-specific context.

      But this would stop the sprawl of custom fields into field configurations across all projects in a Jira instance, and would lessen the probability that, with the creation of each new custom field, we necessarily make Jira slower for everyone.

      Because unfortunately not every organization has a dedicated Jira admin or set of admins that force the reuse of custom fields and actively prevent or discourage their creation.

      Atlassian Update – 29 Oct 2020

      Hi everyone,

      I am happy to announce that this suggestion will be released in Jira 8.14.0.
      We will allow and encourage to specify a context upon custom field creation. This change should mitigate problems related to global custom fields.

      Thank you,
      Szymon Korytnicki,
      Jira Server Developer

            [JRASERVER-71297] Add Config Option To Require Every New Custom Field to Add a Context

            No work has yet been logged on this issue.

              292ec441c8da Szymon Korytnicki (Inactive)
              theosophe741 Michael Spoonauer
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: