Bugzilla 7 Roadmap

Coming (hopefully) 2019. Triage needed.

Bug detail page

• Real time updates (avoid mid-air collisions)
  • Bugzfeed was based on WebSockets which doesn’t work with HTTP/2
  • Web Push is not supported in Mojolicious yet, but server-sent events can be used instead
• Ajaxify comment posting
• Bug tags replacing keywords
• Use syntax highlighting for patches
• Implement attachment overlay (drag & drop, multiple file support)
• Show a mini user profile when hovering over a user

New bug page

• UX analysis
• Merge enhancements from the new-bug page

Advanced search page

• UX analysis

Search results page

• UX analysis
• Ajaxify results loader
• Ajaxify column customizability (use Web Storage API instead of cookies)
• 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)
• Reorganize alternate formats, saved search, etc. as a toolbar
• Mark bugs with new changes/comments on search results
• Re-implement the cookie-based navigation with a client-side local storage, stop using list_id server side

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 webhook support
  • Automatically attach pull request links and close bugs without a 3rd party bot
• GitHub migration support
  • Requires multiple assignees, reviewers field etc. so Bugzilla will be compatible with GitHub
• 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, Read the Docs, in-product pages
• Review page titles and social sharing metadata
• More ideas from BzDeck
• Reboot bugzilla.org