Bulk updating parent links for existing issues

[Coryval25]

I have 2800~ tickets that I need to retroactively add into epics. I have a csv files with all of the values mapped correctly but the bulk import feature doesn't seem to work for this application... What could I be doing wrong? What is the best way to do this without manually updating nearly 3000 tickets.

[Staffan Redelius]

Hi @Coryval25 and welcome to the Community!

I don't use the csv import unless it is absolutely necessary due to the lack of validations during import. It is easy to destroy data and no way to revert the operation.

You should be able to do the update via bulk edit.

1. Create a JQL filtering the issues that should be included in one of the Epics or just list all work items.
2. Click on the three dots in the upper right corner and choose "Bulk change work items"
3. Mark the checkbocks for the items to be included and click next
4. Choose "Edit Issues" and click next
5. Find the field "Change parent" and add the correct Epic
6. Click next and then Confirm to add the Epic as the parent for the issues.

• You need the "Bulk edit" permission to perform the action (Global permission)
• Do a test with a small batch first to see how it works

Let me know if this solves your problem!

Best regards,
/Staffan

[Coryval25]

Hi Staffan, 

My main problem is that I can't really filter on the tickets to get them into their respective categories in order to then do the bulk edit, that's why I'm adding in these epics to categories them for reporting and organisation. 

I'm comfortable doing it the CSV way, I just don't understand why it's not working.

These are the headers I'm using, and based on all the documentation I've been able to find, this should work...

Kind regards,

Cory

[Marc - Devoteam]

Hi @Coryval25 

Welcome to the community.

What s the error you are getting on doing the CVS import and how does your CSV look like?

[Coryval25]

I

I have used this method to update other fields in the past with no issue?

[Staffan Redelius]

I think you should skip the Issue ID for the child andl only use Issue key. Add the issue key for the Epic in the Parent column. The import might get confused if use both Issue Key and Issue ID.

Have you seen this thread? Seems like it covers your scenario
Create/Update Parent-Child linking using CSV Impor... - Atlassian Community

Best regards,
/Staffan

[Coryval25]

Thanks Staffan,

So do I need to include the Epics on their own line of the CSV even though they have already been created? The link you provided didn't make this clear.

Kind regards,

Cory

[Marc - Devoteam]

HI @Coryval25 

Yes, you can leave the Epics out and in the parent ID, set the relevant Epic issue/work item key

On the import use the parent field to map this column in the CSV to.