Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

epic for multiple client

Hi. Here is the request. I have a file that I have exported of our 2022 tasks, and I made updates and need to import as 2023 tasks. The epics have been created and the import file works when I limit it to 1 client, but when I try to use 2 clients, all issues get created but only the 1st client's issues are properly linked to the epics. There must be something wrong with my parent ID or issue ID


@Michael Adegoroye 

Hi Michael:

Welcome to the community.  Can you clarify your ask  - What do you mean by 2 clients?  Can you provide an example on what you are trying to do?

Looking forward to your update, so I can assist you further.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

i want to create new project instance for the incoming year 2023. since we will be dealing with the same epics which we create this year 2022, 

 i have import the epic 2022 and use it to create epic for 2023, i want to create group each epic for a specific client.

for example:

in year 2022, i have 15 client on my Jira board , each has about 100 epics each, i want to repeat the same without starting all over again in year 2023. 

so i import all the instances in year 2022, to use it for 2023, after importing , i could not group the epics according to each client. i.e client 1 to client 15

@Michael Adegoroye -

Just to confirm -

1) You have create a new project and imported all the EPICs from your previous project via bulk issue creation right?

2) The import file only contains EPICs?

Best, Joseph

@Michael Adegoroye -

Forgot to mention are you trying to bulk issue creations for Client 2, but you want those issues to be rolled-up to your specific Epic?

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

this is my import cvs file , so i want use this import to based on the clients, i have up to 15 clients.

@Michael Adegoroye -

So each client has its own CSV?

no all the client is in 1 csv,  the csv contains 26,007 issues and 400 clients

@Michael Adegoroye -

Thanks for the updates.  

In your file, it looks like you have issues that rolls up to Epic via Epic Link column, then you have subtasks that rolls up to the parent issue.

Ideally - 

  1. You should have all the Epics listed first where each of them will have unique Epic Name defined.
  2. For the issues that roll up in to the Epic, you should have the Epic Link column populated using the different Epic Name value from the appropriate Epic.
  3. For the subtask then you will use the ID defined in your IssueID column in the ParentID column appropriately/

Your original export file should also include the IssueType column.  However, it is not there from your image screenshot.

Here is an example of my CSV file for your reference

Issue Type Summary Epic Name Epic Link IssueID Parent ID
Epic Epic 1 MyEPIC1   1  
Epic Epic 2 MyEPIC2   2  
Story Story1   MyEPIC1 3  
Story Story2   MyEPIC1 4  
Story Story3   MyEPIC2 5  
Story Story4   MyEPIC2 6  
Sub-task SubTask1     7 6
Sub-task SubTask2     8 6

You will have to modify your exports and modify it accordingly.  Hope this helps.

Best, Joseph

thanks  let me send the whole export file  to you so that you can  help me analyzed the file, kindly send me your email address.

@Michael Adegoroye -

You can send me an extraction of your actual file to my email  The file should contains your Epic issue, issues roll up to an Epic, and lastly subtasks roll up to the parent issue etc..  I don't need the entire export file.

Best, Joseph


Log in or Sign up to comment

Atlassian Community Events