A few years ago, we worked with an innovative portfolio management solutions company headquartered in the USA with offices in the UK, Europe, and Australia. Their goal was simple:
Move us from Bugzilla to Atlassian JIRA, and integrate JIRA into our current source control system.
Our first piece of business was to conduct a process of requirements discovery for the client’s JIRA installation. We discussed appropriate workflows, custom projects, components, and other configuration parameters with key stakeholders.
Next, we outlined the migration plan from Bugzilla to JIRA including roles, attachments, permissions, and other migration requirements.
Once the key pieces were in place, we installed and configured JIRA then migrated Bugzilla. The migration included two trials to ensure the entire team was comfortable with the new setup. Once the migration was complete, we archived Bugzilla to be used as a source of reference for previous projects.
The engagement concluded with training and a discussion of best practices.
The team was very happy, and their colleagues and clients from around the world were able to share in their collaboration through JIRA.
If you’ve outgrown your bug tracker, it’s time to GO JIRA