nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

External issue ID field purpose

Hayley Rodgers

Hello!

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

Accepted answers

Aron Gombas _Midori_

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.

All comments

Aron Gombas _Midori_

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

This is critical in many situations.

Mariano_gmlums

Hello @Aron Gombas _Midori_ ! Could this also be used for example when I open a ticket with my Internet vendor and they have their own ticket number?

Aron Gombas _Midori_

@Mariano Yes, that would be a very intuitive use of the field, I think.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud