This repository has been archived by the owner on Dec 21, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Bugzilla 7 Roadmap
Kohei Yoshino edited this page May 23, 2019
·
62 revisions
Coming (hopefully) 2020. Triage needed.
- Refine UI design with new custom icons
- Basic mobile support
- Create hovercards for user, bug, product, component
- UX analysis
- 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
- Show bug references inline (auto linking whenever a comment is posted) like GitHub issues
- Use syntax highlighting for patches
- Implement attachment overlay (drag & drop, multiple file support)
- Implement comment reactions with emoji
- UX analysis
- Merge enhancements from the new-bug page
- Support easy emoji input like
:+1:
or:smile:
- Support using user mentions in comments to tag people for needinfo
- UX analysis
- 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
- The initial implementation can just be a bug list taken from My Dashboard plus an
- UX analysis
- 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
- Bugzilla GraphQL API v1
-
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
- 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
- Add support for Google and Firefox accounts?
- Create an entire customer journey map
- Make Component Watching more noticeable so they won’t miss any change
- 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
- Develop UX brief, high-level plan
- Create blog
- Triage UI bugs on Bugzilla
- BMO user survey
- Reboot bugzilla.org
Follow us and join the conversation on Twitter! We are also in #bmo on Mozilla’s internal Slack group.