Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-14675

Lock the Flagged Custom Field used to store impediment value

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • 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.

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

      Problem Definition

      When using JIRA Software, if an issue is 'Flagged' it will create a custom field "Flagged" which belongs to JIRA Software but is not 'Locked'. As this field is not locked it may become subject to deletion by an attempt to clean up custom fields in the environment.

      Suggested Solution

      When the "Flagged field is created, make it locked by default to prevent accidental changes to this field.

      Workaround

      N/A

              Unassigned Unassigned
              majones Matt Jones (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: