Updating dependency link between existing issues using bulk import tool

[Leo Acosta]

We have a project with issues created.  Some are entered as Dependency Issue type; Some as User Stories.  I have a list of stories and their corresponding dependencies that I wish to use to update the existing relationships between them in JIRA.  The sample test file contains the following columns:

Summary,JIRA ID,BLOCKS
Configure Adobe IO import endpoints,DBS-201,DBS-261

Followed the instructions found here in an article on the Atlassian site titled:  "How to Import Issue Links from a CSV File in Jira" and it is not working as expected. 

What happens is the import tool is creating a NEW issue with the dependency rather than linking the two existing issues. 

What am I doing wrong here?

[Morgan DUBUISSON]

Hi, 

<your-site>/secure/admin/ExternalImport1.jspa

CSV Source File : 

id_in;id_out;
GRPN000003-5;GRPN000003-4;

Best regards

[Leo Acosta]

Thanks for the response but that URL doesn't exist in our environment.

[Morgan DUBUISSON]

Hi, 

Sorry this url is for cloud.

This url is for server : /secure/admin/ExternalImport1.jspa is good ? 

Best regards

[Leo Acosta]

The URLS  you sent are the same are they not?

[Morgan DUBUISSON]

Sorry,

I did not see.

Are you a Jira admin?

Can you describe the process you use to access the screen?

There are 2 ways to import one application for admin rights

[Mark Segall]

Hi @Leo Acosta - Can you share a screenshot of the mapping screen?

If you're mapping the Summary/Jira ID to the Summary/Key fields it should not create new issues.

[Leo Acosta]

It's basically three fields and I tried a variety of permutations:

• Summary (left blank and populated with the existing issue summary)
• Issue ID
• Blocker ID

I tried swapping the Issue ID and Blocker ID; I also tried using different Link Types (Blocks vs. Dependency etc) with poor results.

If I leave Summary blank (which has worked in the past and is documented in the instructions) I get an error that the issue can not be created or I get a message that says at least one issue not found (both issues are in my project).  If I populate the Summary with data, the import ends up creating a new issue.

I just want to update links through the import tool on existing JIRA issues.  Has me pulling my hair out.

[Mark Segall]

In your import process, you should be prompted with a screen to map the fields.  Are you making sure that your map looks like this:

• Issue ID = Issue Key
• Summary = Summary

As I understand it, the Summary field cannot be left blank.

[Leo Acosta]

"Issue Key" is not an available field in my instance.  I was using "Issue ID"

[Leo Acosta]

[Leo Acosta]

The article I referenced above indicates that Summary can be left blank if the issue exists but it must be included in the CSV.  Either way - I tried blank and populated and failed.

[Mark Segall]

You need to change the Jira ID to Issue Key.  Issue ID is a system generated ID and will always assume a new issue being created.

[Leo Acosta]

Issue Key is not an available option in the import map.  Could it be a permissions issue?

[Mark Segall]

It may just be Key.  Sorry, it's been a while since I did my last import.

[Leo Acosta]

Don't be sorry.  I really appreciate you trying to help.  There is no field exposed with the word "Key" in it anywhere in the mapping screen.