This repository was 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 6 Roadmap
Kohei Yoshino edited this page Sep 4, 2018
·
93 revisions
What can we do before the release of Bugzilla 6.0 in late 2018?
- Create & implement new style guide
- Add dark theme
- [SHIPPED] UX analysis
- [SHIPPED] Implement compact, fixed header
- [SHIPPED] Remove footer
- [SHIPPED] Implement Requests quick look dropdown
- [WIP] Allow to instantly search recently visited bugs, keywords and components in the quick search bar
- Notify unread requests and mark them in the Requests dropdown
- Redesign mini login widget
-
[SHIPPED] Implement the "new changes since" indicator using the
bug_user_last_visit
API method - [SHIPPED] Give feedback when the Copy Summary button is clicked
- [WIP] Show image/text attachments inline
- UX analysis
- Implement 2-column layout like Xfce's Bugzilla
- Auto-scroll down to new comments/changes
- Implement comment reactions with emoji
- [SHIPPED] Modify product selector layout on Browse and Enter Bug pages
- [WIP] Show number of review/feedback/needinfo in user autocomplete and prevent person from being added if requests are blocked
- Show often/recently used products/components on New Bug page
- [SHIPPED] Enable emoji support
- [WIP] Enable Markdown support
- [WIP] Allow users in editbugs group to edit comments
- Implement text formatting toolbar for comment field
- Support easy emoji input like
:+1:
or:smile:
- Support using user mentions in comments to tag people for needinfo
- [SHIPPED] Check attachment size client-side for too large files
- [SHIPPED] Support drag & drop and and copy & paste on the attachment uploader
- [SHIPPED] Reimplement Google Analytics on bugzilla.mozilla.org
- [SHIPPED] Implement one-click component watching
- Support user name other than email address
- Provide new favicon
- Develop UX brief, high-level plan
- Create blog
- Triage UI bugs on Bugzilla
- BMO user survey
Follow us and join the conversation on Twitter! We are also in #bmo on Mozilla’s internal Slack group.