Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-34766

JIRA should provide the ability to define system issue types which cannot be modified by administrators

    XMLWordPrintable

Details

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

    Description

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

      A plugin (or JIRA) cannot yet prevent a user from deleting special issue types. Some plugins such as JIRA Agile need to define special issue types that other functionality hinges on, for example using them to define custom field contexts.

      Attachments

        Issue Links

          is cloned from

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-32277 JIRA should not re-use issue type IDs after they are deleted

          • Low - Low priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-8435 Greenhopper requires Epic fields even if unlicensed

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-6927 If another Issue type exists with default Epic ID, Greenhopper treats it as the new Epic.

          • Medium - Medium priority issues
          • Closed

          Suggestion - JRASERVER-34766 JIRA should provide the ability to define system issue types which cannot be modified by administrators

          • Closed

          Activity

            People

              Unassigned Unassigned
              mtokar Michael Tokar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: