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

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

chefkoch Jun 04, 2013

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?

2 answers

1 accepted

2 votes
Answer accepted
Matthew Cobby Jun 04, 2013

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

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

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.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

920 views 12 15
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