Recently, we joined an association for physicians and medical students to help them with their current JIRA instance and to migrate a separate team using FogBugz into JIRA. Their needs were simple yet strategic:
We need our entire team on the same system, and to bring in their workflows and processes, to ensure seamless communication with our clients.
Our starting point was their current JIRA implementation, including permissioning, architecture, notifications, etc. This helped us better understand their needs and what was working before we began the migration from FogBugz.
After discussing the migration and planning process with key stakeholders, we reviewed the data mapping strategy that was in place. Once the map was confirmed, we began the migration process.
Since there was a new team joining JIRA, we planned a training session specifically for them. This ensure they were able to transition the terminology in FogBugz to JIRA.
As the training and migration process rolled to a close, we provided an additional block of hours for initial support. This helped ensure any hurdles were quickly crossed and the entire team was able to use JIRA for their specific departmental needs.
If you’ve outgrown your bug tracker, it’s time to GO JIRA