OK. Thanks.

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?

Great stuff!

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.").

Hi Masse

Sorry for the late response, I must have somehow missed your comment.
Creating Epics via CSV Importer and linking them to issues in a single CSV file is also possible - I've pasted the example three comments above.

Cheers,
Przemek

What happens if you let the epic be part of the import instead? Meaning you're project have no issues at all and you link only by name.
That's what I'm trying to do.

This time I did the following steps:

1. Create a project MSP
2. Manually Create Epic with Epic Name "Fix Me ASAP". (It will have issue key: MSP-1)
3. Do a CSV import:

   Issue Type,Epic Link, Summary
   Story, MSP-1        , Some Story one
   Story, Fix Me ASAP  , Some Story two
   Story, fix me asap  , Some Story three
   

   All three stories were created correctly and linked with the epic.

If you still cannot find what's wrong with your import then open a Support Request under this project (with your sample CSV file if possible).

OK. The only difference I can see is that I don't use any project key, project name or or issue keys since I'm importing into a new project.
Could you please confirm that it works for you also without those fields?

EDIT: Probably nothing but for the record I have semicolon as separator.