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

Unable to delete issue type when no scheme is associated

XMLWordPrintable

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

      Issue summary

      The user is unable to delete an issue type if there is no issue type scheme associated with the issue type.

      Steps to reproduce:

      • Delete issue type scheme that has issue types associated with it
      • Go to issue type page
      • Click delete on an issue type that has no issue type scheme associated with it
      • Confirmation dialogue is displayed with no delete button; only cancel

      Expected behavior

      When the confirmation dialogue is displayed, there should be a delete button to confirm the delete action.

      Actual behavior

      There is only a cancel link displayed.

      Error in jlog:
      ERROR sysadmin 686x181x1 1c5djqp 131.103.28.240,59.167.29.217 /secure/admin/DeleteIssueType!default.jspa [webwork.util.ValueStack] query="matchingIssues/empty" {[id="matchingIssues" type="8" values=""]} {[id="empty" type="8" values=""]}
      Confirmation dialogue:

      Workarounds

      • Create a new project
      • Delete the issue type you no longer want
      • Delete the issue type scheme if it is no longer needed

        1. confirmation_screen.png
          confirmation_screen.png
          34 kB
        2. stacktrace.txt
          43 kB

            [JRASERVER-43097] Unable to delete issue type when no scheme is associated

            D. Okon added a comment -

            Same error on JIRA 8.2.3. Is this bug resolving still planned or in progress?

            D. Okon added a comment - Same error on JIRA 8.2.3. Is this bug resolving still planned or in progress?

            Rene C. [Atlassian Support] added a comment -

            Hello, veronique.blick! I'm afraid that Jira 6.4 reached End of life (please see our End of life policy) and it is no longer supported. What we can suggest is to upgrade to a supported version (currently 7.3) and verify if the issue persists. In case you require assistance with the upgrade procedure, experience issues with the upgrade itself, or the issue reported in this bug request is still present after the upgrade, please reach out to our Support team at https://support.atlassian.com/contact/

            Best regards,
            René Chiquete - Atlassian Support.

            Rene C. [Atlassian Support] added a comment - Hello, veronique.blick ! I'm afraid that Jira 6.4 reached End of life (please see our End of life policy ) and it is no longer supported. What we can suggest is to upgrade to a supported version (currently 7.3) and verify if the issue persists. In case you require assistance with the upgrade procedure, experience issues with the upgrade itself, or the issue reported in this bug request is still present after the upgrade, please reach out to our Support team at https://support.atlassian.com/contact/ Best regards, René Chiquete - Atlassian Support.

            Veronique Blick added a comment -

            We are also having this issue and the workaround is not working for us on Jira 6.4.7. 

            Is it possible to get some support? the issue is causing Jira to crash.

            Veronique Blick added a comment - We are also having this issue and the workaround is not working for us on Jira 6.4.7.  Is it possible to get some support? the issue is causing Jira to crash.

            Nicolas Forney added a comment -

            Same error on JIRA 7.2.4. Is this bug going to be resolved in the near future?

            Nicolas Forney added a comment - Same error on JIRA 7.2.4. Is this bug going to be resolved in the near future?

            vitaliy_zapolskyy added a comment -

            Is it all workaround?

            Create a new project - done
            Delete the issue type you no longer want - still see the same error!

            vitaliy_zapolskyy added a comment - Is it all workaround? Create a new project - done Delete the issue type you no longer want - still see the same error!

            Pedro Felgueiras added a comment -

            The bug still alive in the second half of 2016, but the workaround works flawless

            Pedro Felgueiras added a comment - The bug still alive in the second half of 2016, but the workaround works flawless

            Morgan Thunder added a comment -

            2016 now...this bug still very much alive. 6.4.4

            Morgan Thunder added a comment - 2016 now...this bug still very much alive. 6.4.4

            Tony Zhang added a comment -

            confirm this for us as well as 6.4.12

            Tony Zhang added a comment - confirm this for us as well as 6.4.12

            Deleted Account (Inactive) added a comment -

            I can confirm this issue for us, v6.4.7

            Deleted Account (Inactive) added a comment - I can confirm this issue for us, v6.4.7

            Jared Dohrman added a comment -

            Jared Dohrman added a comment -

              Unassigned Unassigned
              mlavender mlavender (Inactive)
              Affected customers:
              11 This affects my team
              Watchers:
              22 Start watching this issue

                Created:
                Updated: