How to add epic link to a task using CSV import?

[João de Sousa Crespo]

Hello,

I've been trying to import a CSV file to my Jira project, linking several tasks to its Epic.

The issue creation goes as planned, with all the necessary fields and issue type (Epic and Task), but the desired link between them isn't created.

I've searched several topics regarding this problem, but none of them helped me resolve my problem. I have event tried using successful exemples from previous topics but, at least in my jira project, they don't work either.

Bellow is a print of the CSV file

I'm planning on importing/creating more than 70K tasks linked to 20 Epics and I can't see any workaround besides this import.

Thank you all in advance

Sincerely,

João Crespo

[João de Sousa Crespo · Accepted solution]

Dear @Jack Brickey , I managed to make it work!

I opened a new project (kanban one) and the task issue had the Epic link field as you mentioned and as I was used to.

In this project the CSV file that didn't work before now works!

Thank you very much for all your help!

[Jack Brickey]

Hi @João de Sousa Crespo , welcome to the community.

Could you please try to use the epic issue key, e.g. ABC-123 rather than name? I also recommend simply attempting to import a single issue until you have the import completely working. Then save the template.

[João de Sousa Crespo]

Hello @Jack Brickey thank you very much for the quick reply.

I've done it before but I did it again as you suggested so that I could show you the error message

This was my new CSV

I changed the epic name and link (the summary remained as it was)

This was the error

I've also tried using parent ID, but apparently that only works with subtasks. Also used Issue Id but again with no succes

Thanks again for the help so far.

[Jack Brickey]

Hi @João de Sousa Crespo , based on the image you provided it seems that you actually used "ABC–123". Please understand that that was just an example. You need to place the actual epic key that you are trying to link the issue to in that cell.  I hope this makes sense?

[João de Sousa Crespo]

Hello @Jack Brickey , sorry for the misunderstanding and for the trouble I'm giving.

I've tried it again without any success.. 

Bellow you can see my new attempt.

1st - I created a new epic so that I could get its name (in this case OP-203)

2nd - I imported a CSV file only to create a Task and linking it to a previous Epic (this would also work for me) 

This did not work.

Now since I knew the next issue ID that would be created (OP-205), I placed it in the CSV and went along as you suggested

Did a new CSV file

This Warning came up when I imported the CSV file

And this was the final result:

The created issue

The created Epic.

[Jack Brickey]

Can you verify that Epic Link field is part of the Create issue screen? You can test this by simply clicking on the plus sign to create a new issue and choose the OP project and task issue type. Do you see the epic link in that screen so that you could add it? If not this likely is the reason. Another test I would suggest....

Start with an existing epic as well as an existing task, however, ensure that that task does not have an associated epic link. Now try to use CSV import to update the task by setting the epic link to the existing epic. Updates using CSV import or achieved by including a column for the issue Key. In this way, the importer understands that you wish to update an existing issue rather than creating a new one. The purpose of this test is simply to see if you can edit the epic link field for an existing issue.

[João de Sousa Crespo]

Thank you in advance @Jack Brickey You are really being a helping hand I really appreciate it.

Regarding the creation of the new issue and seeing ig the Epic link appears I can say it does not! I've worked with Jira in a previous company and I used this field a lot so I already saw that problem. I tried to solve it using the Issue type screens and adding it to the issue but it continues to not appear to me in the creation process (note: I import the CSV file trough the External System Import, otherwise the Epic name and Epic link would not be appear to me as fields to be mapped).

I also preformed your test suggestion. I believe I did it correctly but it did not go accordingly

CSV

Issues created

It created two new issues none of them relating to each other.

[Jack Brickey]

Regarding last test use the issue key not issue ID.

regarding getting the Epic link into the screen please try the following...

1. go to Project settings
2. select Screens
3. find the screen for Create issue and click on pencil
4. Verify the Epic link is in the list if not add it

Retry creating an issue and check for Epic link. If not there check the Layout under settings. Please note that you should have a project specific screen scheme rather than updating the default since it may be used by other projects and you generally don't want/need the Epic link on the create screen IMO.

[João de Sousa Crespo]

Dear @Jack Brickey , sorry for my mistake. I posted the wrong picture before. Nevertheless, I tested it again without any success.

Here you can see the correct CSV

This is the XML that I exported so that I could see the Issue Key

And here are the warning and the issues that were created

It created two new issues were the issue ID was the issue Key (maybe I'm getting these two wrong)

Regarding the project settings and screens (I believe the trick might be here) I couldn't find the screens as you mentioned

My project settings page shows no screens (as seen below)

The only way to find the screens is like this

This is what comes back

When I try to change the Custom Fields, this is where the Epic name and link appear. But they are locked (I don't know if this is normal or not)

[João de Sousa Crespo]

Also, I compared XML files for the Epic and task before and after linking them manually.

The diference is as follows

<parent id="10379">OP-10373</parent>

This is what appears in the child issue (Task), the Epic remains the same.

I've tried updating the fields using the parent ID but without success

[Jack Brickey]

Hi @João de Sousa Crespo , So it appears that you were actually using a team managed project. Some of what I have conveyed was specific to a company managed project. The most important difference here is that the field for The most important difference here is that "epic link" does not apply to TMP projects. Rather you should use "parent" to convey the Epic for an issue. Now, I have never attempted a CSV import for TMP projects as I rarely use them. However, I expect it should work just the same if you choose the proper field mapping. Also, I'm not sure what you have the first line in your CSV for the Epic. Please attempt the following:

1. Start with an existing epic.
2. Create a CSV for a single issue that you wish to associate to that epic.
3. Use parent as the field and put in the epic issueKey, e.g. Abc-123
4. when mapping the field, be sure to map your parent CSV column to the Parent field

[João de Sousa Crespo]

Dear @Jack Brickey Thank you for all you help.

My project is now runnig! Hoping to show it to the board and get them to sign a full license of Jira and confluence.

Again, many thanks to you and to the community