Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

External issue ID field purpose


Just doing a bit of an audit of my company's Jira and I've come across stacks of "External issue ID" custom fields. It looks like one new field is being created by JIM each time we import a set of issues using the External System Import feature. 

Can I delete them? What is their purpose?

Screen Shot 2021-12-08 at 5.01.51 pm.png


1 answer

1 accepted

0 votes
Answer accepted

I think the purpose of that field is giving you backward traceability and searchability.

For example, if you used a different issue tracker in the past and you had a bug with ID=12345, then when you import it to Jira, it will receive a Jira-style issue key like "FOO-567", but the importer will save its old ID to that custom field. Because this info is preserved, you can search for the issues based on their old IDs even in Jira.

This is critical in many situations.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

👋 Looking for 15-20 volunteers to test Atlassian training content

Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...

884 views 25 28
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you