[original issue at https://jira.atlassian.com/browse/GHS-6995]
When importing issues through CSV files, it is not possible to import the following Epic fields:
- Epic Colour
- Epic Link
- Epic Name
- Epic Status
The only one field that is possible to map is Epic/Theme.
I have also tried changing the scope of those custom fields to Global, but it didn't help.
- relates to
-
JRASERVER-67230 JIRA External System Import (JIM) can create new options for locked custom fields
-
- Gathering Impact
-
[JIM-988] Greenhopper Epic fields cannot be imported to JIRA through CSV
| Link | New: This issue relates to JRASERVER-67230 [ JRASERVER-67230 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
| Workflow | Original: JIM Project Workflow (Software Simplified) [ 1607113 ] | New: JIM - workflow v2 [ 1610862 ] |
We usually release the plugin at the end of the iteration (+/- two days), so the fix should be available on Marketplace near 13-17.05.2014. If you are using JIRA OnDemand, you would have to wait additional two weeks, due to our additional QA Process for OnDemand environment.
By the way. Assuming these things will be fixed within the next iteration, when are they expected to be released?
Thanks for your feedback, you are right - the importing process could be improved, that's why I've created a new issue for our importer: JIM-1269. Under this issue I try to fix all of the annoying things about importing epics/stories via CSV Importer. I will schedule that improvement for the next iteration: 1.05.2014 - 15.05.2014
Cheers,
Przemek
I've done some testing and came to the conclusion that epic linkage does not work if there's more than one epic with the same name in the system.
For example, let's say there's an epic with epic name "MyEpic" in an existing project. If I try to do a csv import into a new project with data containing an epic named "MyEpic" and a story with epic linkage "MyEpic", I will get the error "Cannot add value [ MyEpic] to CustomField Epic Link in Issue AAA-XXX. Probably value was in incorrect format".
So not only is the error message misleading but once again the problem with Jira handling Epics as globals come into play.
Since I choose what project to import my csv into it would make sense that Jira looks into that project only.
Another problem is that in my csv, the epics need to be imported before the stories, otherwise I get the same error. Michal Kujalowicz latest comment suggests this should not be a problem ("Epics are imported in the first step and then next issues are properly linked to them.").
OK. Thanks.