Auto-tools/Projects/Bugzilla 2013Q2

Make bugzilla more user-centric and to improve the various workflows for the various roles.

Breakdown and End Game

Right now, bugzilla is a one-size fits all system. And so it does some workflows well, it does some things less well since it tries to treat all roles with the same set of functionality. We can improve use cases and workflows across the board by making Bugzilla more user centric (right now you can think of it as very bug centric). We want to highlight the different roles, and streamline the workflows for each one.

Since this is our first step in this direction there are a set of "enabling" changes we want to make to bugzilla to advance our ability to scale and perform so that we can be more innovative with the various roles and workflows we want to create.

Milestones

By the end of the quarter, we want to update the code review UI on bugzilla to make it more modern and feature comparable with our competitors, complete and deploy the tracking flags optimization & migration, complete and deploy the native REST API optimization

Milestone 1 Tentative Dates: April 1 - April 12

• Release plan for user workflows
• Complete Tracking flags work, plan for migration
• Perform first step of updates for code review functionality in bugzilla

Milestone 2 Tentative Dates: April 15 - April 26

• Deploy migration for tracking flags
• Complete native REST API integration work
• Begin Bugzilla profile low level integration
• Complete Bugzilla profile HTML Mocks
• Continued work on code review changes

Milestone 3 Tentative Dates: April 29 - May 9

• Wire Bugzilla profile mocks into true frontend
• Delpoy native REST changes
• Deploy Code Review changes