Auto-tools/Projects/Bugzilla 2013Q2

< Auto-tools‎ | Projects

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

Contents

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.

The project name for these whiteboard flags is "bugzilla".

Milestone 1 Tentative Dates: April 1 - April 12

  • [MISSED] Finish implementation of new-style tracking flags.

Milestone 2 Tentative Dates: April 15 - April 26

  • (carry over) [MISSED] Finish implementation of new-style tracking flags.
  • [MISSED] Deploy new tracking flags feature alongside old tracking flags.
  • [MISSED] Complete tracking-flags migration script.
  • [DONE] Finish vagrant box.

Milestone 3 Tentative Dates: April 29 - May 10

  • (carry over) [MISSED] Finish implementation of new-style tracking flags.
    • Nearing end of review cycles.
  • (carry over) [MISSED] Deploy new tracking flags feature alongside old tracking flags.
  • (carry over) [MISSED] Complete tracking-flags migration script.
    • Nearing end of review cycles.
  • [MISSED] Complete testing of tracking-flags migration script.
  • [MISSED] Fix splinter papercuts.
    • About half of the bugs done.

Milestone 4 Tentative Dates: May 13 - May 24

  • (carry over) [DONE] Finish implementation of new-style tracking flags.
  • (carry over) [MISSED] Deploy new tracking flags feature alongside old tracking flags.
  • (carry over) [DONE] Complete tracking-flags migration script.
  • (carry over) [MISSED] Complete testing of tracking-flags migration script.
  • (carry over) [DONE] Fix splinter papercuts.
  • [MISSED] Complete Native REST API implementation.

Milestone 5 Tentative Dates: May 27 - June 7

  • (carry over) [MISSED] Deploy new tracking flags feature alongside old tracking flags.
  • (carry over) [MISSED] Complete testing of tracking-flags migration script.
  • [MISSED] Complete Native REST API implementation.
  • [MISSED] Deploy Native REST API implementation to dev server for testing.
  • [ON TRACK] Start work on new code-review tool.

Milestone 6 Tentative Dates: June 10 - June 21

  • (carry over) [ON TRACK] Deploy new tracking flags feature alongside old tracking flags.
  • (carry over) [ON TRACK] Complete testing of tracking-flags migration script.
  • (carry over) [ON TRACK] Complete Native REST API implementation.
  • (carry over) [ON TRACK] Deploy Native REST API implementation to dev server for testing.* Deploy Native REST API to production.
  • Perform tracking-flags migration with IT. (?)
  • Finish new code-review tool.

Milestone 7 Tentative Date: June 24 - June 28

  • Deploy new code-review tool.