Skip to content
This repository was archived by the owner on Dec 21, 2019. It is now read-only.

Bugzilla 7 Roadmap

Kohei Yoshino edited this page Oct 8, 2018 · 62 revisions

Coming (hopefully) 2019. Triage needed.

Bug detail page

New bug page

Comment editing

Advanced search page

  • UX analysis

Search results page

  • UX analysis
  • Modernization
    • Ajaxify results loader, drop legacy server push (multipart/x-mixed-replace) technology
    • Ajaxify column customizability (use Web Storage API instead of cookies)
    • Re-implement the cookie-based navigation with a client-side local storage, stop using list_id server side
  • Enhancements
    • Reorganize alternate formats, saved search, etc. as a toolbar
    • Make table header fixed
    • Implement filter (at least Status)
    • Implement simple list for mobile as well as Detail View that can be switched from the traditional tabular List View (as seen in BzDeck, Buggy and JIRA)
    • Mark bugs with new changes/comments on search results

Home page

  • Personalized inbox like BzDeck
    • The initial implementation can just be a bug list taken from My Dashboard plus an <iframe> showing header-less bug page

Preferences page

  • UX analysis

Better tools

  • Enhanced quick search bar
  • Kanban board
    • Make it easier to manage bugs in particular products
  • Redesign profile page
    • Add contribution graph like GitHub
  • Product/component dashboards
    • Replace the current component description pages
    • Show open/closed bug charts, top contributors, recent bugs

Integrations

  • Bugzilla REST API v2
  • GitHub integration
    • Webhook support: Automatically attach pull request links and close bugs without a 3rd party bot
    • Migration support: Requires multiple assignees, reviewers field etc. so Bugzilla will be compatible with GitHub
    • and more...
  • Slack integration

Even more

  • Research and optimize the onboarding experience, for both Mozilla employees and contributors
    • Talk to Mozilla’s internal teams handling these areas (stakeholder interviews)
    • Implement password generator or requirements checker
  • Organize scattered documents/help on Wiki (BMO & upstream), Read the Docs (BMO & upstream), in-product pages
  • Review page titles and social sharing metadata
  • Review status, resolution (bug life cycle) and other fields
  • More ideas from BzDeck
  • Reboot bugzilla.org
Clone this wiki locally