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

Issue Types all showing as not being associated with a Scheme after deleting an Issue Type

XMLWordPrintable

      The user is unable to create an issue after an issue type has been deleted. The Issue Type screens shows all the issue types as not being associated with an issue type scheme, however the issue type schemes are still present.

      Steps to reproduce:

      • Delete an issue type
      • GET A 500 ERROR (not reproducible every time)
      • Click delete on the issue type that was being deleted
      • Get the below error with only a cancel button

      Expected behavior
      When clicking on the Create button, issue type drop down should be visible.
      The default issue type scheme should not have double up issue types.
      The issue types should all show as being associated with an issue type scheme.
      Deleting an issue type should have a delete and cancel button present.

      Actual behavior
      (creating an issue) There is only a project drop down
      (viewing issue type scheme) The default issue type scheme is showing two of most issue types (e.g. "Issue", and then "Issue" again)
      (viewing issue types) All issue types are showing as not having any associated issue type scheme
      (deleting an issue type) There is only a cancel link displayed.

      Confirmation dialogue:

      Workaround:

      • Open the Default Issue Type Scheme
      • Click the Save button
      • Everything returns to normal

        1. confirmation_screen.png
          confirmation_screen.png
          34 kB

            [JRASERVER-43557] Issue Types all showing as not being associated with a Scheme after deleting an Issue Type

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.04
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2831246 ] New: JAC Bug Workflow v3 [ 2922555 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2552241 ] New: JAC Bug Workflow v2 [ 2831246 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1542689 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2552241 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Eric S (Inactive) made changes -
            Component/s Original: Administration [Deprecated] [ 10271 ]
            Eric S (Inactive) made changes -
            Component/s New: Project Administration - Issue Types [ 43296 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 873970 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1542689 ]

            Jared Dohrman added a comment -

            Thanks Oswaldo,

            Will do

            Thanks,
            Jared.

            Jared Dohrman added a comment - Thanks Oswaldo, Will do Thanks, Jared.

            Oswaldo Hernandez (Inactive) added a comment -

            Hi jared.dohrman,

            Index optimisation is off an removed from JIRA since JIRA 5.1.6 (see JRA-29487 for details). Consequently, I suspect that this is probably not an issue in modern versions of JIRA.

            Please do let us know if you run into it ever again after upgrading your instance

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi jared.dohrman , Index optimisation is off an removed from JIRA since JIRA 5.1.6 (see JRA-29487 for details). Consequently, I suspect that this is probably not an issue in modern versions of JIRA. Please do let us know if you run into it ever again after upgrading your instance Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

              Unassigned Unassigned
              a0dea38eac93 Jared Dohrman
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: