When importing a single project request type is no match

[Kimi Nakashima]

We've been trying to import a single project from our backup instance to our dev instance. It seemed like it worked except that for some reason the Request type didn't get populated for any of our issues. We next tried to do a csv import to populate the Request type, but it didn't populate the field either. We can fix them manually but we've got a lot of issues so it'll take quite a bit of time to do plus leaves us open to error.

Does anyone have any suggestions on how to fix this?!

[Amanda Kirk · Accepted solution]

@Kimi Nakashima 

I am assuming the source and destination projects are both JSD projects? Otherwise, this information would likely be lost.

There is a documented bug in regards to this.  Please see https://jira.atlassian.com/browse/JSDSERVER-1335 for more details. 

This bug reported states that when JIRA imports issues, instead of the expected Customer Request Type, issues are imported without the Customer Request Type altogether. 

You will need access to the DB to attempt this workaround, but essentially it details how to replace the value in the CSV with the "correct format" value from JIRA's database.

[Kimi Nakashima]

@Amanda Kirk Brillant! We had to adjust the sql query a bit since we aren't using postgresql, but we managed and it worked!  

Thank you very much! 

[Amanda Kirk]

Nice! Glad to hear :)