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

Default Issue Type Scheme does not have all issue types and issues are not migrated to an existing issue type

    XMLWordPrintable

    Details

      Description

      Summary

      In some cases, the default Issue Type Scheme does not have all the issues types present in the instance and, when changing the Issue Type Scheme of a project to the Default Issue Type Scheme, the change occurs but the user is not prompted about the issue type migration of existing issues that have issue types that are no longer applicable.

      Steps to Reproduce

      1. Create a dummy project.
      2. Create a test issue choosing an issue type that is not present in the Default Issue Type Scheme.
      3. Go to the project settings> Issue types and change the issue type scheme to the Default Issue Type Scheme.

      Expected Results

      • The user should be prompted to migrate the issue type of the existing issue to an issue type available in the Default Issue Type Scheme OR the Default Issue Type Scheme should have all the issue types available by default.

      Actual Results

      • The issue type scheme is changed to Default Issue Type Scheme and the issue keeps with the issue type that is not present in the Default Issue Type Scheme.

      Notes

      • This can cause issues to search for these issues, for instance, using a query like:
      assignee is empty

      Workaround

      • Create a copy of the Default Issue Type Scheme, add the missing issue types in the copy and associate the scheme with your project/s.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              skorte Soane Korte (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: