Need help understanding externalId used in JSON import

The JSON import examples use an externalId field to identify issues to be linked. But evidence suggests that using this causes a custom field to be created during the import. We already have an external ID custom field and want to avoid creating a duplicate custom field (JSON is not an option if we can't avoid this).

  1. Is there a way to link issues without using externalId? (Can we use key instead?)
  2. Is externalId a "special" field created by the JSON importer to support linking of issues?

1 answer

1 accepted

0 votes
Accepted answer
Mirek Community Champion Jun 30, 2014

Hi Bejamin,

Ad 1. I am not aware of any method to link without using externalID

Ad 2. externalid is a special field created automatically by the importer.

In my opinion there is no issue with that you wil have two fields called externalID... importer will create a second one and it will not use your original field. After successful import you can just delete the field. There is no reason to keep in in the system.

Everything should be fine. You can do some test on a test system first to be sure if the procedure is working for you.

I hope that this will help you.



Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,943 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you