How to bulk edit the issues to JIRA by importing excel format to JIRA

Archana
Contributor
April 16, 2019

Hi All, 

Daily we are importing excel sheet to create issues in bulk..First day it goes well in creating issues.Second day excel sheet consists of Already existing records, some fields(like owner change or number field for particular issue change)changes in a bulk..Bulk edit by find issue we can do, but we have many records to be edited so it may take more time..so is there any way to edit by direct importing excel sheet to JIRA ?? and i need following  changes before creating issues on second day to JIRA

1. Only new records should be uploaded as tickets to JIRA. Older ones as created on first  day itself.

2. It should update only changed fields if any to the already created issues on first day. As we have one key field as IMEI number which will not change..but owner of that device may change.

3. It should delete some records if that process is sent to the main source.

 

Can anybody helps me 

Thanks :)

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted
shetty
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 16, 2019

Hi

 

We can do it

by adding column issue key in CSV file

and make sure that it is mapped correctly

Archana
Contributor
April 16, 2019

If i add and upload the file, it will not overwrite(it will not edit the created issue) instead it will create new issue

Like Avinash Kumar likes this
shetty
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 16, 2019

No, just remove every thing from file

add only Issue Key(Respective issue ex;-UBP-96) and the fields that you want to edit as columns and let the summary field be there as it was because it is required for import

I have done it before the same way

attaching screenshot for your reference i just wanted to edit description field so i have added issue key and description as i want it to be

48.JPGIt won't create any additional issues in project

Like Niclas Lund Stisager likes this
Archana
Contributor
April 16, 2019

Thanks a lot Ramesh..It workd

I have one more query..My sheet consists of some 1000 records including edited ones and new ones ....from one site we are donwloading the template and uploading it to the JIRA. We have one field(IMEI Number)as unique it wont change..so if there is same IMEI number in the field then instead of creating new issue, it should update(edit) that created issue. And for rest all new IMEI numbers it should create new issues..

So can we have any option in JIRA ?

Anna Bolen-Testa
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 7, 2019

Hello,

How are you importing with the Issue Key?  I am trying to use the "Import Issues from CSV" and it is not giving me Issue Key as a field I can map?  Am I trying to import from the wrong place?

Thanks,

Anna

Like # people like this
Andy Reising September 14, 2021

Does anyone know the answer to Anna's question? 

I cannot map to the Issue Key field, which is what I'm trying to match on to update existing issues.

The import screen says: 

A JIRA Summary field mapping is required to enable import.

Like ardian.krivca likes this
Anna Bolen-Testa
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 14, 2021

I was able to give my file with the mappings to our administrator and he was able to import my updates for me. So it may just be a permissions issue. 

Like # people like this
ardian.krivca
Contributor
July 12, 2022

do you know he was able to find a "issue key". I am not a admin, and I dont see "issue key".