Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3.1.0-OD-12, 3.2.0-OD-01, 3.2.0-OD-07
-
Severity 3 - Minor
-
4
-
Description
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Summary
When creating a Service Desk project for the first time, if a default issue type that would be created during the project creation process already exists, it must match the intended case sensitivity or project creation will fail.
For example:
If an issue type exists titled "INCIDENT", project creation will fail when creating an IT Service Desk as the process is attempting to create an issue type titled "Incident". This would also fail with any other case configuration that differs from the default "Incident", such as "INCident","InciDENT",etc..
Environment
- JIRA Service Desk v3.2.0-OD-01-001
- JIRA Service Desk v3.1.0-OD-12-001
Steps to Reproduce
On an instance that currently doesn't contain a Service Desk project:
- Create an Issue Type titled "INCIDENT"
- Attempt to create an IT Service Desk
- Observe error:
Hmm... we couldn't create your project due to an unknown error. Try refreshing the page to start again.
Expected Results
Projected should be created, using existing issue type's case structure.
Actual Results
The below exception is thrown in the JIRA log file:
2016-02-02 11:23:40.130911500 2016-02-02 11:23:40,122 http-nio-2990-exec-1301 ERROR sysadmin 683x221172x1 1ar6uib 4.15.43.214,165.254.226.114,127.0.0.1 /rest/project-templates/1.0/templates [c.a.jira.project.ProjectCreateRegistrarImpl] 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 2016-02-02 11:23:40.130915500 java.lang.IllegalStateException: An issue type with the name 'Incident' exists already. 2016-02-02 11:23:40.130977500 at com.atlassian.jira.config.DefaultIssueTypeManager.createIssueTypeAndAddToDefaultScheme(DefaultIssueTypeManager.java:141) 2016-02-02 11:23:40.130978500 at com.atlassian.jira.config.DefaultIssueTypeManager.createIssueTypeAndAddToDefaultScheme(DefaultIssueTypeManager.java:171) 2016-02-02 11:23:40.130978500 at com.atlassian.jira.config.DefaultIssueTypeManager.createIssueType(DefaultIssueTypeManager.java:98) 2016-02-02 11:23:40.130986500 at sun.reflect.GeneratedMethodAccessor14289.invoke(Unknown Source) 2016-02-02 11:23:40.130987500 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2016-02-02 11:23:40.130988500 at java.lang.reflect.Method.invoke(Method.java:497) 2016-02-02 11:23:40.130996500 at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26) 2016-02-02 11:23:40.130996500 at com.sun.proxy.$Proxy73.createIssueType(Unknown Source) 2016-02-02 11:23:40.130997500 ... 2 filtered
Notes
This has been verified on all issue types associated with the default Service Desk project templates. Project creation does not fail with the same scenario for JIRA Software and Business project templates.
Workaround
- Edit the existing Issue Type to the default intended case sensitivity, and re-attempt project creation.
- If you would prefer a different case sensitivity of your issue types, you can create the service desk project and then edit the issue type afterwards.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is related to
-
-
- Gathering Impact
-
- relates to
-
-
- Closed
-
- was cloned as
-
QUALITY-248 Loading...