During the import from Mantis current the following two fields are created: * External Issue ID * External Issue URL We will disable (delete later) the URL field after the import, because the old bug tracker won't be online anymore at some point. The Issue ID we would like to keep to look up the old ID and for redirecting to the new JIRA id. But what is the best way to store this ID? * It should be read-only and no issues created in future should be able to add an ID to the fieldd. * It should be able use it within the search. I was able to keep this field enabled, but hide it from all the screens, but then I also found some additional custom field types: * Bug Import Id A read-only custom field that points back to the previously imported bug id. * Import Id A read-only custom field that points back to the previously imported bug id. What are these for?

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; } } }

What is the best way to store the issue ID from the previous bug tracker?

chefkoch

During the import from Mantis current the following two fields are created:

External Issue ID
External Issue URL

We will disable (delete later) the URL field after the import, because the old bug tracker won't be online anymore at some point.

The Issue ID we would like to keep to look up the old ID and for redirecting to the new JIRA id.

But what is the best way to store this ID?

It should be read-only and no issues created in future should be able to add an ID to the fieldd.
It should be able use it within the search.

I was able to keep this field enabled, but hide it from all the screens, but then I also found some additional custom field types:

Bug Import Id
A read-only custom field that points back to the previously imported bug id.
Import Id
A read-only custom field that points back to the previously imported bug id.

What are these for?

Accepted answers

MatthewC

You can just usethe External Issue ID and don't put it on any of the edit screens, only on a view screen. That way no user can edit it through the normal front end. It's technically it might still be editable through the remote API but I suspect that since it's not on an edit screen, the remote API may check this (need to verify this). It would then turn up in search as expected

All comments

MatthewC

Christian Czaia [Decadis AG]

That's exactly what we did after a bugzilla migration.

Pawel Niewiadomski

Bug Import Id and Import Id are custom field types that were originally used by JIRA Importers Plugin when it was bundled with old JIRA 3.x and 4.x. We don't advise using them anymore. It's better to use text custom field type which is searchable. Those custom field types (Bug Import Id and Import Id) will eventually be removed from JIRA at some point as they are not used anymore.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

import

mantis