OK. Thanks.

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.

Hi Mattias,

I just double check the import of Epic Links in the CSV importer - everything seems to be working. This is one of the CSV files that I've prepared for my tests:

ProjectKey,ProjectName,IssueKey,IssueType,Summary          ,EpicName,EpicStatus ,EpicLink
DDD       ,        ddd,   DDD-1,Epic     ,Some Awesome Epic,EpicName,Done       ,        
DDD       ,        ddd,   DDD-2,Task     ,Some Task        ,        ,           ,EpicName
DDD       ,        ddd,   DDD-3,Bug      ,Some Bug         ,        ,           ,DDD-1   
DDD       ,        ddd,   DDD-7,Bug      ,Some Bug         ,        ,           ,EpicEpic
DDD       ,        ddd,   DDD-5,Task     ,Some Task 2      ,        ,           ,epicepic
DDD       ,        ddd,   DDD-6,Bug      ,Some Bug  2      ,        ,           ,DDD-4   
DDD       ,        ddd,   DDD-4,Epic     ,Another Epic     ,EpicEpic,To Do      ,        

In EpicLink column you can specify EpicName or Issue Key of the epic. If you still cannot perform an import, please let me know - we will create a separated Support Request for you and we will try to help you with any problems connected to the import process.

I would like to add that I manually added the "Epic Name" column, so that my epics will get their epic name set.
But still, the epic link for all my other issues won't work.
I get error on all stories saying:
"Cannot add value [ [SomeEpicName] ] to CustomField Epic Link in Issue AAA-XXX. Probably value was in incorrect format".

I would really appreciate some help on this.

My problem started by not being able to link epics with issues upon import.
Then I realized that the epics had no epic name field in my csv.
I am exporting all columns/fields to excel but only epic link is included.

Hi Masse

This issue is about importing issues via CSV Importer. As I believe you are trying to export issues to a file. Did you try export issues to Excel (All fields)? This should provide you a correct file even with all JIRA Agile fields. More informations can be found in our Documentation

Hi.
I choose to export all columns but still I can only see Epic Link in my exported csv. I'm missing all the other epic fields.
What might be wrong?
I'm on JIRA v6.3-OD-02-026

cheers

I verified this once again (6.2 OD, 6.1.4, 6.0.8). Epics are imported in the first step and then next issues are properly linked to them.
What is interesting is that in case the 'issue key' field is mapped then order of issues is also preserved. This might be the option when this order is important.

I agree that for second issue we could have separate bug. This issue will be closed.

pborkowski, according to the testing notes:

Import Epic Link for non-Epic issue type - does not import for issues declared before epic in csv file

Testing Notes:

• Import Epic with Name, Colour, Status for Epic issue type
• Import Epic Link for non-Epic issue type
• Try to import unsupported values for fields: Epic Colour, Epic Status
• Try to import Epic with Epic Name which duplicates with existing
• Try to import into Locked Epic field (e.g. Epic Link in Epic, Epic Name in issue other than Epic)
• Crosscheck above situations also when editing existing epic with import
• Check for CSV + other importer (if possible)

Added support for fields: Epic Colour, Epic Link, Epic Name, Epic Status
Description for each of these fileds can be found in documentation:
https://confluence.atlassian.com/display/AGILE/JIRA+Agile+-+JIRA+Configuration
Epic Link - allows linking issues to Epic via Issue Key or Epic Name

Sprint Custom Field is still disabled for import, I've created separated issue for that:
https://ecosystem.atlassian.net/browse/JIM-1091

I managed to work arroud this issue by using the "Atlassian Command Line Interface".
This tool allows you to batch import from csv including custom fields.

any update on this issue?

In the meantime I managed to import the Epics and populating the "Epic Name" field using the JIRA Command line client.

It's not currently scheduled for any nearest release. We are gauging the interest though of the customers, so keep providing your feedback.

This is a essential feature to us.
Could you please let us know, what the implementation plans are?