Upload Epic, Task and Sub task via CSV is not working

[Fred van Beek]

I am not working as a system administrator. but as a normal user.
I only have access to 1 project and start the csv import from the create button in the top menu bar.

I want to upload a file with tasks and subtask, under an already existing Epic.

1. Tasks cannot be related to parent Epic
   For the task, I put as Parent ID the Epic name.
   The validation process responds: Issue 'Task 1' doesn't have Subtask Issue Type, its Parent Id mapping will be ignored.
   So how can I relate tasks to existing Epics? Based on the validation reply it is not possible to relate tasks to Epics...(
   
   
2. Should the tasks and the sub tasks be in the same or in separate files. 
   
   
3. Subtasks are not uploaded. Error;doesn't have a valid Parent Id selection
   I tried uploading 2 subtasks. For 1 Subtask 1 specified the task name as Parent ID.
   For the other I specified the Issue ID of the task as parent ID.
   None worked,

See upload file below

Issue Type, Issue ID, Parent ID, Summary ,        Description ,    Assignee , Reporter
Task ,         100 ,       TestEpic ,  Task1 ,              Task1 ,             fvb ,           fvb
Subtask ,   1001 ,      100 ,          Sub of task 1 , Sub of task 1,  fvb ,           fvb
Subtask ,   1002 ,      Task1 ,       sub2 of task 1,sub2 of task 1, fvb ,          fvb

[auj012]

Hi Daniel

  Any update on this topic ? Where U able to create tasks under a epic via csv ?

Please share I am getting the same error

Thanks

[Daniel Alonso]

Thanks for checking in.
I reached out to my Jira Admin and got no response.
So unfortunately no real solution here.

However I found a decent workaround:

After you upload your tasks, you can click the link to view them.
In this view, you can do a bulk change to set their Parent to the Epic you want.
It only takes maybe a few more minutes to do this extra step, so it's still pretty efficient.

For my use-case all of my tasks are generally assigned to the same Epic after I upload them, but I can imagine it being more tedious if you need to assign them to different Epics.

[auj012]

Thank you Daniel. On my systems  "Components" was a mandatory field , once I added and mapped it I was able to create it.

Thanks

[Ismael Jimoh]

Hi @Fred van Beek 

With regards your CSV import,

1. With Epic, please use the epic link field as the parent/child fields are reserved for Task -> sub-task association. As you are bot the admin, make sure you can create and associate the issues from the Jira project’s create issue screen first else your import will potentially fail.
2.  You can put tasks and sub-tasks in the same file but you must make sure your tasks come before any sub-tasks that will be related to them. 
3. Your sub-task shouldn’t need an issue id . All it requires is a parent id. Do not use issue summary for parent id also.

read more about csv import here: https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html

Regards

[Fred van Beek]

Hi Ismael, Thanks for your quick answer

Actually I was looking for a field Epic Link ( I have seen when someone logged in as admin), but that field is not available for linking in my view (see screen print below)

I put a value in the parent ID of the taskm because it is mandatory. When not putting a value for parent ID for the task, an error appears> Fatal error during import: Parent Issue cannot be null


Other things are understood.
I adjusted file as suggested.

Issue Type,Issue ID,Epic link  ,Parent ID,Summary ,Description ,Assignee,Reporter
Epic          ,           1,               ,               ,Test Epic ,Test Epic      ,fvb         ,fvb
Task          ,       100,Test Epic ,               ,Task1       ,Task1           ,fvb         ,fvb
Subtask    ,     1001,               ,100         ,Sub1        ,Sub1           ,fvb         ,fvb
Subtask    ,     1002,               ,100         ,Sub2        ,Sub2           ,fvb         ,fvb

[Ismael Jimoh]

Hi @Fred van Beek 

Can you confirm that the epic link field appears when you click the create button in JIRA?

Without this field appearing, you will not be able to import it since you are not the system admin of the instance and the basic import, follows the fields provided on the create screen.

See below from my test:

Regards.

[Fred van Beek]

I can con firm that the Epic Link field does NOT APPEAR

Seems like a bug to me.

I was able to create tasks and subtasks, but could not link the task to an Epic.
Same for stories. Can create but cannot link to the Epic.

In the end I used upload to create stores and sub tasks, but linked the stories manually.

why are mapping fields not same as in Supervisor Mode.
Upload of project data is a user action.
Normal user upload should work as well.

[Ismael Jimoh]

The reason as I mentioned is your view is the same as that of someone who clicks create on the UI. You will only be able to map fields that are on the projects create issue screen.

The Admin view supersedes this assuming the admins know what they are doing.

To fix your issue, ask your JIRA administrator to add the Epic Link field to the create issue screen of your project.

Once this is done, you should be able to import epics.

[Daniel Alonso]

I have this same issue and I have the Administrator role for my project.
Seems like a bug to me.

I could not find a way to add the Epic Link field to the create issue screen.
I am working in a next-gen project.

(Not sure if there is a cross-project kind of role that I don't have.)

I'll be manually setting the Epic from the backlog in the meantime.
It seems strange to be able to set the Epic after creation, but not before.

Additionally I don't see a "Subtask Issue Type" field either, so even if Parent Id is the correct field I'm not sure it would be usable.

[Ismael Jimoh]

@Daniel Alonso ,

Here I would check first with the JIRA Administrator to ensure that the Epic Link field is on the create issue screen. If it is, then this would normally work.

It has been a while so I cannot say for certain without testing this out first.

Regards.

[Daniel Alonso]

Thanks, will do. I did  not know that JIRA Administrator is different from someone who has the Admin role for a given project.
I found the "Contact Jira Administrator" page, so I'll reach out from there.
I'll post again here if I get a meaningful resolution.