Priorities for the Bugs Team
|Complete initial API export||2.2.1|
|Package-specific reporting guidelines
Bonus points for a syntax for including screenshots
Being able to say and record "this bug affects me to"
|Parse HWDB info I
Parsing out USB/PCI IDs and BIOS fields.
|HWDB: Get number of users affected by a bug tied to a device||2.2.2||-||-||4||-|
|HWDB: Include DMI and lspci information in HWDB submissions||implemented in 2.2.2, but superseeded||-||-||4||-|
|HWDB: Find out which computers have a certain device||2.2.2*||-||-||4||-|
|HWDB: Get number of users using a driver||2.2.2||-||-||4||-|
|Inline editing of bug summary||2.2.2|
|Link to file bugs upstream||2.2.2||1||-||13||-|
|Link to search bugs upstream||2.2.2||1||-||13||-|
|Enable search and filebug links for a project manually||2.2.2||1||-||13||-|
|Enable search and filebug links for a project automatically||2.2.2||1||-||13||-|
Ensuring bug activity captures all bug changes
|Bug Activity UI Interleaving
Displaying activity in the comments view
Actually using OfficialBugTags for something!
|Inline editing of bug description||2.2.4*|
|Bug page remake||2.2.4*|
|Bug page Q&A||2.2.5*|
Using the recorded information and display it as a kind of ''hotness''
|Duplicate-detection inside launchpad
Scavenge Launchpad bugs with similar contents to the bug displayed and easily mark dupes
|Sanitize targeting to series/milestones
Basically only use series tasks for backports
|Personal bug dashboard
Add screen and bug listings for managing your bugs
|Fix issues with bug nominations discussed at UDS
Bug 253597, bug 253600, bug 253608, bug 253612, bug 110195, bug 253610
|Negated Tags in Searches
Allow searching for bugs with some tags, but without others
Unsubscribing implicit subscribers from specific bugs
|Importing from tarballs
Making it easier for people to import project bugs into Launchpad for bug tracking
|UI for submitting bugs upstream II
Using our Trac and Bugzilla plugins
Let users see and understand what search filters are on, and clean up default search URLs, https://bugs.edge.launchpad.net/malone/+bug/28697
|Status/Milestone updates for milestoned bugs
Simple UI to update selected bugs
|Track QA status
Allow the OEM team to track QA tasks in Launchpad, without using tags.
|No more Confirmed
With Me Toos and Triaged, removed this confusing status
|Quick summary/description/tags editing
Allowing people to change these fields without two pageloads. Estimated excluding AJAX
Allowing us to track expired bugs separately from invalid, including a textual rationale
|Email first-time bug-reporters
A welcome message and guide to triaging process
|Bugtask forwarding relationships
Being able to say "This bug is in Ubuntu" or "This bugtask needs an upstream task" or "This bugtask is waiting for an uptream task"
|Version-tracking of bugs
Being able to specify that a bug is present or was introduced in version X, and later fixed in version Y
|Flip Incomplete to New
Automatically flip bugs from Incomplete when information is provided.
|CSV bug lists
Offering a CSV export containing bug metadata for download through the web
|Customizable search columns
Being able to specify what columns you'd like to see in the bug list
Allow special users to submit private bugs, and make it clear what consequences result of marking a public bug private
|Proactive bug imports
Enabling complete syncs from plugin-enabled sites
Pre-requisite for the triage report and useful to external report builders
Marking and hiding irrelevant comments. See bug 220535. This is for admins only to start with.
UI to allow the user to say "I don't know/Hardy/Intrepid/..."
|Project group dupefinder support||5.5||24||-||-||4|
|Specific status change UI
Guide people to our intended workflow; allow people to add a comment and click a button to do a certain status transition
|Triage throughput report
See Triaging QoS Report
|Import a remote bug UI
One-push importing and task-annotation from Debbugs & Bugzilla
|Duplicate-detection across bugtrackers
Scavenge upstream and downstream bugtrackers for possible duplicates of bug report; on-demand and as a second step to bug reporting
|Make HWDB submissions searchable by kernel version
Extract the kernel version used when the HWDB submission, displaying it, and allow searches to be filtered by it
|Code review UI
Allow code review of patch attachments, feature-parity with Bugzilla (shouldn't this be in codehosting?)
|Better package name UI guidance
If the user selects "don't know" then lead him to an explanation
|Duplicate bug watch workflow
When a bugwatch is linked to multiple bugs, notify/warn users (how? when?)
Provide a repository of crashes linked to bug reports, possibly integration with Breakpad?
|Link HWDB submissions to bug reports
This would be a first step, just linking a submission to a bug report. The developers would still have to download the data and look at it offline.
|Timebomb New bugs
After 6/N months, all New bugs become Incomplete
Marking a bug as frozen, disallowing new comments from non-bug-team-members
|Link hardware component to a bug report
This would allow us to be more specific at saying which hardware is affected.
|Qualifying bug reporters
Redirect non-qualified people to answers; based on Karma, Ubuntu Members, Referees, etc.
- Mark, MOTU, Martin Pool (Bazaar), Pat M. (Ubuntu Solutions Group), Henrik (Ubuntu), Kiko (Launchpad)
(2 story points ≈ work required for bug 4593)
New unsorted items
|File bugs on packages in PPAs|
|HWDB: Correlate hardware configurations with bug reports|
- API will be very young and is likely to require time and bugfixes as usage ramps up.
- Our Bugtracker plugin support is in a similar situation, though less likely to require a large amount of fixes or modification.
- Consider the distro team wishlist too.
- Steve M and Pat M (USG):
- mass bug editing number 1 request (setting and changing milestone for multiple bugs, adding a comment and changing status for a set of bugs)
- date range queries for open, modified and verified
- navigation within a set of query results (a next/previous bug session hanger)
- performance as a major issue (cited 10-30s page loads)
- cited the lack of ordering of bug queries using columns
- would like to be able to define fields per-project for new bug reports (my idea is to have a little schema language, request the information from the reporter, and then dump it into the description -- kiko)
- Mentioned a verified status for post-release QA.
- also cited performance (cited 3-second page loads)
- Auto-detecting threads related to bug reports
- Mass bug editing would be high on our list
- Consider https://wiki.canonical.com/BazaarInfrastructureNeeds
- Performance also cited
Bug tracker integration candidates
- Java bugtracker integration (firstname.lastname@example.org)
- MySQL bugtracker integration
- The Bug Genie
- Google Code