Multiple Issue updates with CSV

[Peter]

Hi there,

I've tried to update some Userstories with the CSV uploader.

Therefore i've done the following steps:

1. Exported some Userstories to CSV

2. Edited the summary field

3. uploaded the changed CSV file (External System Import, CSV, Field mapping, Issue Key mapping)

--> Everything has been changed successfully

----Now the problem---

If i try to run a secound update on the same userstories, Jira will reply "n of n issues have been skipped because they already exist in destination projects."

Steps i've further done:

4. changed the already existing CSV file again (summary field)

5. Tried step 3 with the newer changed CSV file again

Expected: I can update as many times as i want via CSV upload

Situation: I can only update once.

Is there a workaround or anything wrong in my process?

[Cristian Rosas [Tecnofor]]

Hi @Peter,

I don't know the problem but I'm interested on why does it happen. It can be problematic if that situations start happening to me!

When I want to update an issue via CSV, I map the Issue Key and the Summary, but leaving Summary in blank. As fas as I understand, when you do something like this, you can't update these tickets because Jira tries to create them with the same ID?

[Peter]

Hi @Cristian Rosas [Tecnofor]

not exactly.

I try to go more into detail:

1. Export some issues to CSV

2. Edit Value for fields (e.g. Summary, Design Doc ID) in CSV [not leaving anything blank]

3. Update the Fields via External System Import

4. Map --all-- CSV Columns to Jira Fields [inclusive Issue Key AND Summary]

5. Upload

--> Will work

6. Export the same issues as before to CSV

7. Edit Value for fields (e.g. Summary, Design Doc ID) in CSV [not leaving anything blank]

8. Update the Fields via External System Import

9. Map --all-- CSV Columns to Jira Fields [inclusive Issue Key AND Summary]

10. Upload

--> Jira will reply "n of n issues have been skipped because they already exist in destination projects."

11. Take the under 6. edited file again

12. Update the Fields via External System Import

13. --ONLY-- map Issue Key and the edited Columns (e.g. Summary, Design Doc ID)

--> will work

My Problem is, i want to update dataset, in which i dont know exactly what values are changed - so i need to map all Jira Fields.

I hope you got the problem?!

[Cristian Rosas [Tecnofor]]

Mmm that's weird... I have no problem when updating any field via CSV. Can you share screenshots or some example csv? (with false data, I don't care). I'll show you a simple example:

I can update the same Keys changing the value of the custom or system fields as many times as I want. Take note that I always let summary field as blank

[Peter]

@Cristian Rosas [Tecnofor]

I've actually kind of solved the Problem.

It happens only by mapping the field "Issue ID" and it only happens for already updated Issues.

--> For 1st time updates i can map the Issue ID field, if it comes to 2nd update Jira will reply the "already existing phrase" if "Issue ID" is mapped.

Works only once:

definitly works

 

Is this a feature or a bug? 

[Cristian Rosas [Tecnofor]]

That should be asked to Atlassian, maybe they can answer that question