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

Lock Issue Types From Being Edited


    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • 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 Server. Using JIRA Cloud? See the corresponding suggestion.

      Problem Definition

      Some Issue Types, such as Epic and Story, indicate that they should not be edited however there is nothing which prevents that from occurring.

      Use case:
      Customer edited the Epic Issue Type to "New Type." If viewing an Agile Scrum Backlog, "New Type" is not displayed as Epics are Hidden from the Backlog.

      Suggested Solution

      Implement a "locking" feature similar to non-editable System Fields to prevent these Issue Types from being edited


      Update the modified Epic Issue Type back to "Epic" and create a New Issue Type

            Unassigned Unassigned
            scranford Shawn C
            0 Vote for this issue
            2 Start watching this issue