IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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

      Workaround

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

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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

                Workaround

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

                        Unassigned Unassigned
                        scranford Shawn C
                        Votes:
                        2 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            scranford Shawn C
                            Votes:
                            2 Vote for this issue
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: