Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-4853

Unable to create project in Jira Service Desk due to incorrect issue type name.

XMLWordPrintable

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

      Summary

      When attempting to create a JIRA service desk project the creation fails and users receive the following error:

      "Hmm... we couldn't create your project due to an unknown error. Try refreshing the page to start again."

      Environment

      Cloud - JIRA Service Desk Application v3.3.0-OD-1000.940.0

      Steps to Reproduce

      1. Change the name of any issue type that's used by service desk and already exists.
      2. e.g: Change the 'Sub-task' issue type name to 'Sub-Task'
      3. Try to create a service desk project

      Expected Results

      The project should be created.

      Actual Results

      The below exception is thrown in the JIRA log file:

      2017-02-23 13:24:54.187883500 2017-02-23 13:24:54,127 http-nio-2993-exec-23 ERROR sysadmin 804x11495x1  104.192.142.137 /rest/project-templates/1.0/templates [c.a.j.project.ProjectCreateRegistrarImpl.privacy-safe] The handler with id com.atlassian.jira.project-templates-plugin:apply-project-template-handler threw an exception while handling a notification about a project being created

2017-02-23 13:24:54.187885500 java.lang.IllegalStateException: An issue type with the name 'Sub-task' exists already.

2017-02-23 13:24:54.187886500 at com.atlassian.jira.config.DefaultIssueTypeManager.createIssueTypeAndAddToDefaultScheme(DefaultIssueTypeManager.java:130)

2017-02-23 13:24:54.187928500 at com.atlassian.jira.config.DefaultIssueTypeManager.createIssueTypeAndAddToDefaultScheme(DefaultIssueTypeManager.java:160)

2017-02-23 13:24:54.187929500 at com.atlassian.jira.config.DefaultIssueTypeManager.createIssueType(DefaultIssueTypeManager.java:93)

2017-02-23 13:24:54.187929500 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

2017-02-23 13:24:54.187935500 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

2017-02-23 13:24:54.187935500 ... 1 filtered

      Notes

      This only happens when you're trying to create your first project.

      Workaround

      • Change the issue type that was modified, changing the name back to default.

       

            Unassigned Unassigned
            akasper André K. (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: