Status: Gathering Impact (View Workflow)
Affects Version/s: 4.8.0, 3.3.0, 3.5.1, 3.12.2, 3.15.3, 4.5.2, 4.7.0
Fix Version/s: None
Component/s: Global Configuration
Support reference count:21
Symptom Severity:Severity 3 - Minor
Bug Fix Policy:
Steps to reproduce
- Export issues created in a Service Desk from JIRA to csv
- Import issues back into JIRA mapping the Customer Request Type field to the one exported by JIRA
JIRA imports issues successfully with the expected Customer Request Type
Issues are imported but without the Customer Request Type
The following is seen in the log
replace the value in the CSV with the "correct format" value from JIRA's database with the following SQL query.
It should be all lower cases, with '-' instead of spaces and preceded by the project key and a slash.
For example, "Get IT Help" in project TST will need to be replaced as "tst/get-it-help"
The custom request type will have some random hash values, example: "tst/bc4b6686-1b4a-4f26-84d3-ecf184bafdd9".
In this case, user wouldn't understand what is the correct request type for each string value.
To get the full list of request types + string value for each project, this query can be used: