Ubuntu Wiki

MOTU

QATeam

Feature

Comments

Estimated Effort*

3

Tag Discipline

Actually using Bug Tags for something!

8

-

Workload estimation

Story points/hours

-

Importing from tarballs

Making it easier for people to import project bugs into Launchpad for bug tracking

7

-

Project group dupefinder support

5.5

2

Complete Activity Log

Ensuring bug activity captures all bug changes

12

Bug Activity UI Interleaving

Displaying activity in the comments view

9

7

Me Too

Being able to say and record "this bug affects me to"

6

Bug Freezing

Marking a bug as frozen, disallowing new comments from non-bug-team-members

6

Expired bugs

Allowing us to track expired bugs separately from invalid, including a textual rationale

4

-

Flip Incomplete to New

Automatically flip bugs from Incomplete when information is provided.

Timebomb New bugs

After 6/N months, all New bugs become Incomplete

17

No more Confirmed

With Me Toos and Triaged, removed this confusing status

-

Ignore Subscriptions

Unsubscribing implicit subscribers from specific bugs

6

Import a remote bug UI

One-push importing and task-annotation from Debbugs & Bugzilla

15

Email first-time bug-reporters

A welcome message and guide to triaging process

5

18

Capture Distro Series When Filing Bugs

UI to allow the user to say "I don't know/Hardy/Intrepid/..."

3

11

Collecting Bug Statistics

Pre-requisite for the triage report and useful to external report builders

14

Triage throughput report

See Triaging QoS Report

13

UI for submitting bugs upstream I

Offering convenience links for sites not running our plugins

UI for submitting bugs upstream II

Using our Trac and Bugzilla plugins

-

Qualifying bug reporters

Redirect non-qualified people to answers; based on Karma, Ubuntu Members, Referees, etc.

12

Better package name UI guidance

If the user selects "don't know" then lead him to an explanation

1

Package-specific reporting guidelines

Bonus points for a syntax for including screenshots

5-6

Proactive bug imports

Enabling complete syncs from plugin-enabled sites

-

Better Privacy Workflow

Allow special users to submit private bugs, and make it clear what consequences result of marking a public bug private

7

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

-

Code review UI

Allow code review of patch attachments, feature-parity with Bugzilla

20

Explicit Search Filtering and Clean URLs

Let users see and understand what search filters are on, and clean up default search URLs, https://bugs.edge.launchpad.net/malone/+bug/28697

9

5

Duplicate-detection inside launchpad

Scavenge Launchpad bugs with similar contents to the bug displayed and easily mark dupes

3

9

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

Crash reporting

Provide a repository of crashes linked to bug reports, possibly integration with Breakpad?

8

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"

-

Negated Tags in Searches

Allow searching for bugs with some tags, but without others

2

-

Duplicate bug watch workflow

When a bugwatch is linked to multiple bugs, notify/warn users (how? when?)

Quick summary/description/tags editing

Allowing people to change these fields without two pageloads.

5

-

Status/Milestone updates for milestoned bugs

Simple UI to update selected bugs

20

Fix issues with bug nominations discussed at UDS

Bug 253597, bug 253600, bug 253608, bug 253612, bug 110195, bug 253610

19

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

-

Customizable search columns

Being able to specify what columns you'd like to see in the bug list

-

CSV bug lists

Offering a CSV export containing bug metadata for download through the web

16

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.

4

Parse and search HWDB info I

Parsing out USB/PCI IDs and BIOS fields, allowing submissions to be searched by hardware component.

Link hardware component to a bug report

This would allow us to be more specific at saying which hardware is affected.

10

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