-
Bug
-
Resolution: Fixed
-
Low
-
3.3.0
-
Severity 3 - Minor
-
Summary
When the indexing language is not the same as the language that has been used during installation, JSD projects creations breaks with errors.
- New SD projects have many errors, statuses, customer notifications, and empty queue page.
- Creating a sample project results in errors in regards of importing.
Steps to Reproduce
- Start up an instance in English and create a business project at startup.
- In settings change indexing language to Spanish.
- Create a JSD project:
- Create a sample project.
OR - Create other JSD projects with approvals.
- Create a sample project.
Expected Results
The new JSD project should be created without errors.
Actual Results
For the 1st scenario, we can see the following in atlassian-jira.log:
c.a.j.p.i.i.importer.impl.AbstractDataImporter$1Thread[http-nio-8080-exec-1,5,main]] Importing issue: [externalId='null', summary='Photo editing software request'] 2017-01-30 18:29:01,438 http-nio-8080-exec-1 WARN eseidel 1109x3317x1 1ticebt 0:0:0:0:0:0:0:1 /rest/jira-importers-plugin/1.0/demo/create
This is an example of one of the issues that is being imported (it will show up in the screen shot later). Immediately after, the following warning is thrown:
2017-01-30 18:29:01,438 http-nio-8080-exec-1 WARN eseidel 1109x3317x1 1ticebt 0:0:0:0:0:0:0:1 /rest/jira-importers-plugin/1.0/demo/create [c.a.j.p.i.i.importer.impl.AbstractDataImporter$1Thread[http-nio-8080-exec-1,5,main]] Custom Field [ Customer Request Type ] was not found and cannot be created
That's followed by:
2017-01-30 18:29:01,488 http-nio-8080-exec-1 ERROR eseidel 1109x3317x1 1ticebt 0:0:0:0:0:0:0:1 /rest/jira-importers-plugin/1.0/demo/create [c.a.j.p.i.i.importer.impl.AbstractDataImporter$1Thread[http-nio-8080-exec-1,5,main]] Error importing issue [externalId='null', summary='Photo editing software request'] com.atlassian.jira.plugins.importer.external.ExternalException: Status [ Erledigt ] does not have a linked step in the [ jira ] workflow. Please map to a different status.
The issues are actually imported however:
2017-01-30 18:29:02,139 http-nio-8080-exec-1 INFO eseidel 1109x3317x1 1ticebt 0:0:0:0:0:0:0:1 /rest/jira-importers-plugin/1.0/demo/create [c.a.j.p.i.i.importer.impl.AbstractDataImporter$1Thread[http-nio-8080-exec-1,5,main]] 40 issues successfully created
For the 2nd scenario, new SD projects have many errors, statuses, customer notifications, empty queue page such as:
Request Form contains configuration errors The following fields don't have any values set: ¿Qué sistema? As a consequence these Request Forms cannot be used successfully by customers: Solicitar una nueva cuenta To repair these Request Forms, add values for these fields on this project's components page.
Workaround
- Change the indexing language back to English which is the same as the system language, run a full re-indexing and then create a Service Desk project
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-4908] Fix translated string compare to english for statuses
Erik Seidel
added a comment - In addition I had to mention that deleting projects does not do a clean job as well. For example FIELDS, Field Configuration Schemes, Field Configurations, SCREENS, Issue Type Screen Schemes, View Screen Schemes and more still got artefacts that we had to clean manually…
Erik Seidel
added a comment - In addition I had to mention that deleting projects does not do a clean job as well. For example FIELDS, Field Configuration Schemes, Field Configurations, SCREENS, Issue Type Screen Schemes, View Screen Schemes and more still got artefacts that we had to clean manually…
Hello Mogavenasan
We started to built our IT-Support using JSD now with the Server based Version v7.1.9#71013-sha1:1aa0586 - but I had to tell you that the artifacts left from deleted projects is still an existing issue in your software.
Cheers,
Erik