We are in the process of doing a very large import of old Bugzilla bugs. We've imported everything and now people are beginning to look through the issues in JIRA to make sure nothing got lost in the import. (These bugs were from a version of Bugzilla that was too old for the JIRA importer to deal with.) As part of the import, we created project keys and used the old Bugzilla ID to create the issue keys. We also stored the old Bugzilla ID as the external issue ID. Our Bugzilla users want to be able to quickly search for issues in JIRA just with the Bugzilla ID since that's what shows up in e-mail trails and in code. Obviously, they don't want to have to guess at what the project key might be. We've figured out how to do this using advanced search, but it's frustrating for some users to have to go through those extra steps. Is it possible to tie the external issue ID into quick search, perhaps with something like "e:<external issue ID>"?
There didn't seem to be a good solution to this. We ended up putting all of the imported issues into one project called "Bugzilla Bugs". Project admins could move the issues into a different project after the import was completed, or they could clone the old issue into a new issue in the appropriate project. This has worked well for us.
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...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG