Diff for "VersionThreeDotO/Bugs"

Not logged in - Log In / Register

Differences between revisions 4 and 27 (spanning 23 versions)
Revision 4 as of 2008-11-26 20:21:29
Size: 11314
Editor: bjornt
Comment:
Revision 27 as of 2009-04-03 14:52:29
Size: 13476
Editor: bjornt
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
|| M || T || B || S || U || L || Feature || SP || Released ||
|| || || || || || || Complete initial API export || X ||
|| || || || || || || Socially engineering our plugins into adoption || ||
|| 5 ||11 || - || || 1 || -
|| **Package-specific reporting guidelines**\\Bonus points for a syntax for including screenshots || [[VersionThreeDotO/BugsEstimations#package-specific-guidelines|5-6]] ||
|| 3|| 9 || 13|| || 7 || 1 || **MaloneMeToo I**\\Being able to say and record "this bug affects me to" || [[VersionThreeDotO/BugsEstimations#malone-me-too|3]] || 2.1.11 ||
|| 3|| 9 || 13|| || 7 || 1 || **MaloneMeToo II**\\Using the recorded information and display it as a kind of ''hotness'' || [[VersionThreeDotO/BugsEstimations#malone-me-too|3]] ||
|| - || || - || || 4 || - || **Parse HWDB info I**\\Parsing out USB/PCI IDs and BIOS fields. || || 2.1.11 ||
|| - || || - || || 4 || - || **Search HWDB info I**\\Allowing submissions to be searched by hardware component. || ||
|| 1 || || - || || 13|| - || **UI for submitting bugs upstream I**\\Offering convenience links for sites not running our plugins || ||
|| 23|| 2 || 5 || || 2 || 3 || **[[/CompleteActivityLog]]**\\Ensuring bug activity captures all bug changes || [[VersionThreeDotO/BugsEstimations#complete-activity-log|12]] ||
|| 11|| 1 || - || || || || **Fix issues with bug nominations discussed at UDS**\\[[https://launchpad.net/bugs/253597|Bug 253597]], [[https://launchpad.net/bugs/253600|bug 253600]], [[https://launchpad.net/bugs/253608|bug 253608]], [[https://launchpad.net/bugs/253612|bug 253612]], [[https://launchpad.net/bugs/110195|bug 110195]], [[https://launchpad.net/bugs/253610|bug 253610]] || ||
|| 25|| 4
|| 11||   || 3 || 2 || **[[/TagDiscipline]]**\\Actually using OfficialBugTags for something! || [[VersionThreeDotO/BugsEstimations#tag-discipline|8]] ||
|| 13||12 || 16|| || - || 5 || **Negated Tags in Searches**\\Allow searching for bugs with some tags, but without others || [[VersionThreeDotO/BugsEstimations#
negated-tags|2]] ||
|| - || 5 || - || || - || - || **[[/IgnoreSubscriptionsRevenge]]**\\Unsubscribing implicit subscribers from specific bugs || [[VersionThreeDotO/BugsEstimations#ignore-subscriptions|6]] ||
|| 15|| || 3 || || 5 || 6 || **Duplicate-detection inside launchpad**\\Scavenge Launchpad bugs with similar contents to the bug displayed and easily mark dupes || [[VersionThreeDotO/BugsEstimations#duplicate-detection|3]] ||
|| -|| || - || || - || 8 || **Importing from tarballs**\\Making it easier for people to import project bugs into Launchpad for bug tracking || [[VersionThreeDotO/BugsEstimations#
importing-from-tarballs|7]] ||
|| 2 || || - || || || - || **UI for submitting bugs upstream II**\\Using our Trac and Bugzilla plugins || ||
|| 7 || || 14|| || 20||10 || **[[/ExplicitSearchFilteringAndCleanURLs|/ExplicitSearchFilteringAndCleanURLs]]**\\Let users see and understand what search filters are on, and clean up default search URLs, https://bugs.edge.launchpad.net/malone/+bug/28697 || [[VersionThreeDotO/BugsEstimations#clean-urls|9]] ||
|| 22|| 3 || 6 || || || 5 || **[[/ActivityLogInterleaving|Bug Activity UI Interleaving]]**\\Displaying activity in the comments view || [[VersionThreeDotO/BugsEstimations#bug-activity-ui-interleaving|9]] ||
||
10|| || 2 || 1 || - ||11 || **Status/Milestone updates for milestoned bugs**\\Simple UI to update selected bugs || [[VersionThreeDotO/BugsEstimations#mass-edit|20]] ||
|| 18|| || 7 || || 17||12 || **No more Confirmed**\\With Me Toos and Triaged, removed this confusing status || ND ||
|| 9 || || 1 || || || 9 || **Quick summary/description/tags editing**\\Allowing people to change these fields without two pageloads. Estimated excluding AJAX || [[VersionThreeDotO/BugsEstimations#quick-bug-edit|5]] ||
|| -|| || 12|| || 6 || 5 || **Expired bugs**\\Allowing us to track expired bugs separately from invalid, including a textual rationale || [[VersionThreeDotO/BugsEstimations#expired-bugs|4]] ||
|| 4 || 8 || - || || 15|| - || **Email first-time bug-reporters**\\A welcome message and guide to triaging process || [[VersionThreeDotO/BugsEstimations#email-first-time|5]] ||
|| 6 || || - || || 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" || ||
|| - || || 8 || 6 || 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 || ||
|| 20|| 6 || - || || - || 7 || **Flip Incomplete to New**\\Automatically flip bugs from Incomplete when information is provided. || ND ||
|| - || || 4 || 2 || - || - || **CSV bug lists**\\Offering a CSV export containing bug metadata for download through the web || ||
|| - || || 9 || 5 || - || - || **Customizable search columns**\\Being able to specify what columns you'd like to see in the bug list || ||
|| - || || - || 4 || - ||14 || **[[/BetterPrivacyWorkflow]]**\\Allow special users to submit private bugs, and make it clear what consequences result of marking a public bug private || [[VersionThreeDotO/BugsEstimations#better-privacy-workflow|7]] ||
|| 8
||14 || - || || || - || **Proactive bug imports**\\Enabling complete syncs from plugin-enabled sites || ||
|| - || || - || || 11||13 || **[[/CollectingBugStatistics]]**\\Pre-requisite for the triage report and useful to external report builders || [[VersionThreeDotO/BugsEstimations#collecting-bug-statistics|ND]] ||
|| -||10 || 15|| || || - || **[[/FixingIrrelevantComments]]**\\Marking and hiding irrelevant comments. See [[https://bugs.edge.launchpad.net/malone/+bug/220535|bug 220535]]. This is for admins only to start with. || [[VersionThreeDotO/BugsEstimations#deleting-comments|2]] ||
|| - || 7 || - || || 18|| - || **[[/CaptureDistroSeriesWhenFilingBugs]]**\\UI to allow the user to say "I don't know/Hardy/Intrepid/..." || [[VersionThreeDotO/BugsEstimations#capture-distroseries|3]] ||
|| 24|| || - || || - || 4 || **[[https://bugs.edge.launchpad.net/malone/+bug/174443|Project group dupefinder support]]** || [[VersionThreeDotO/BugsEstimations#project-group-dupefinder|5.5]] ||
|| - ||13 || 16|| || || - || **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 || ||
|| 16|| || - || || 14|| - || **Triage throughput report**\\See [[https://blueprints.edge.launchpad.net/launchpad/+spec/qastats-bug-triage|Triaging QoS Report]] || ||
|| 17||15 || - || || || - || **Import a remote bug UI**\\One-push importing and task-annotation from Debbugs & Bugzilla || ||
|| - || || - || || 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 || ||
|| - || || - || || 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 || ||
|| - || || 10||   || - || - || **Code review UI**\\Allow code review of patch attachments, feature-parity with Bugzilla (shouldn't this be in codehosting?) || ||
|| - || || - || || 12|| - || **Better package name UI guidance**\\If the user selects "don't know" then lead him to an explanation || ||
|| 12||   || - || || - || - || **Duplicate bug watch workflow**\\When a bugwatch is linked to multiple bugs, notify/warn users (how? when?) || ||
|| 14|| || - || || || - || **Crash reporting**\\Provide a repository of crashes linked to bug reports, possibly integration with Breakpad? || ||
|| -|| || - || || - ||15 || **Workload estimation**\\Story points/hours || ||
|| - || || - || || 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. || ||
|| 19|| || - || || || - || **Timebomb New bugs**\\After 6/N months, all New bugs become Incomplete || ||
|| 21|| || - || || || - || **[[/BugFreezing]]**\\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. || ||
|| Feature || SP || Released || M || T || B || S || U || L ||
|| Complete initial API export || || **2.2.1** || || || || || || ||
|| **Package-specific reporting guidelines**\\Bonus points for a syntax for including screenshots || [[VersionThreeDotO/BugsEstimations#package-specific-guidelines|5-6]] || **2.2.1** || 5 ||11 || - || || 1 || - ||
|| **MaloneMeToo I**\\Being able to say and record "this bug affects me to" || [[VersionThreeDotO/BugsEstimations#malone-me-too|3]] || **2.1.11** || 3|| 9 || 13|| || 7 || 1 ||
|| **Parse HWDB info I**\\Parsing out USB/PCI IDs and BIOS fields. || || **2.1.11** || - || || - || || 4 || - ||
|| HWDB: [[/StoryCards#hwdb-affected-users|Get number of users affected by a bug tied to a device]] || || **2.2.2** || - || || - || || 4 || - ||
|| HWDB: [[/StoryCards#hwdb-dmi-lspci|
Include DMI and lspci information in HWDB submissions]] || || **implemented in 2.2.2, but superseeded** || - || || - || || 4 || - ||
|| HWDB: [[/StoryCards#h
wdb-filter-by-device-and-system|Find out which computers have a certain device]] || || 2.2.2* || - || || - || || 4 || - ||
|| HWDB: [[/StoryCards#hwdb-users-using-driver|Get number of users using a driver]] || || **2.2.2** || - || || - || || 4 || - ||
|| [[/StoryCards#inline-edit-bug-summary|Inline editing of bug summary]] || || **2.2.2**|| || || || || || ||
|| [[/StoryCards#link-to-upstream-filebug|Link to file bugs upstream]] || || **2.2.2**
|| 1 || || - || || 13|| - ||
|| [[/StoryCards#link-to-upstream-searchbugs|Link to search bugs upstream]] || || **2.2.2** || 1 || || - || || 13|| - ||
|| [[/StoryCards#set-remote-product-manually|Enable search and
filebug links for a project manually]] || || **2.2.2** || 1 || || - || || 13|| - ||
|| [[/StoryCards#set-remote-product-automatically|Enable search and
filebug links for a project automatically]] || || **2.2.2** || 1 || || - || || 13|| - ||
|| **[[/CompleteActivityLog]]**\\Ensuring bug activity captures all bug changes || [[VersionThreeDotO/BugsEstimations#complete-activity-log|12]] ||**2.2.3** || 23|| 2 || 5 || || 2 || 3 ||
|| **[[/ActivityLogInterleaving|Bug Activity UI Interleaving]]**\\Displaying activity in the comments view || [[VersionThreeDotO/BugsEstimations#bug-activity-ui-interleaving|9]] || **2.2.3** || 22|| 3 || 6 || || || 5 ||
|| **[[/TagDiscipline]]**\\Actually using OfficialBugTags for something! || [[VersionThreeDotO/BugsEstimations#tag-discipline|8]] || **2.2.3**|| 25|| 4
|| 11||   || 3 || 2 ||
|| [[/StoryCards#filebug-improvements|Filebug-workflow improvements]] || || 2.2.4* || || || || || || ||
|| [[/StoryCards#inline-edit-bug-description|Inline editing of bug description]] || || 2.2.4* || || || || || || ||
|| [[/StoryCards#ajaxify-bug-page|Bug page remake]] || || 2.2.4*|| || || || || || ||
|| **Bug page Q&A** || || 2.2.5* || || || || || || ||
|| **MaloneMeToo II**\\Using the recorded information and display it as a kind of ''hotness'' || [[VersionThreeDotO/BugsEstimations#malone-me-too|3]] ||2.2.5* || 3|| 9 ||
13|| || 7 || 1 ||
|| **Duplicate-detection inside launchpad**\\Scavenge Launchpad bugs with similar contents to the bug displayed and easily mark dupes || [[VersionThreeDotO/BugsEstimations#duplicate-detection|3]] ||2.2.5* || 15|| || 3 || || 5 || 6 ||
|| **Sanitize targeting to series/milestones**\\Basically only use series tasks for backports || || 2.2.6* || || || || || || ||
|| **Personal bug dashboard**\\Add screen and bug listings for managing your bugs || || 2.2.6* || || || || || || ||
|| **Fix issues with bug nominations discussed at UDS**\\[[https://launchpad.net/bugs/253597|Bug 253597]], [[https://launchpad.net/bugs/253600|bug 253600]], [[https://launchpad.net/bugs/253608|bug 253608]], [[https://launchpad.net/bugs/253612|bug 253612]], [[https://launchpad.net/bugs/110195|bug 110195]], [[https://launchpad.net/bugs/253610|bug 253610]] || || || 11|| 1 || - || || || ||
|| **Negated
Tags in Searches**\\Allow searching for bugs with some tags, but without others || [[VersionThreeDotO/BugsEstimations#negated-tags|2]] || || 13||12 || 16|| || - || 5 ||
|| **[[/IgnoreSubscriptionsRevenge]]**\\Unsubscribing implicit subscribers from specific bugs || [[VersionThreeDotO/BugsEstimations#ignore-subscriptions|6]] || || - || 5 || - || || - || - ||
|| **Importing from tarballs**\\Making it easier for people to import project bugs into Launchpad for bug tracking || [[VersionThreeDotO/BugsEstimations#importing-from-tarballs|7]] || || -|| || - || || - || 8 ||
|| **UI for submitting bugs upstream II**\\Using our Trac and Bugzilla plugins || || || 2 || || - || || || - ||
|| **[[/ExplicitSearchFilteringAndCleanURLs|/ExplicitSearchFilteringAndCleanURLs]]**\\Let users see and understand what search filters are on, and clean up default search URLs, https://bugs.edge.launchpad.net/malone/+bug/28697 || [[VersionThreeDotO/BugsEstimations#clean-urls|9]] || || 7 || || 14|| || 20||10 ||
|| **Status/Milestone updates for milestoned bugs**\\Simple UI to update selected bugs || [[VersionThreeDotO/BugsEstimations#mass-edit|20]] || || 10|| || 2 || 1 || - ||11 ||
|| **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 || ND || || 18|| || 7 || || 17||12 ||
|| **Quick summary/description/tags editing**\\Allowing people to change these fields without two pageloads. Estimated excluding AJAX || [[VersionThreeDotO/BugsEstimations#quick-bug-edit|5]] || || 9 || || 1 || || || 9 ||
|| **Expired bugs**\\Allowing us to track expired bugs separately from invalid, including a textual rationale || [[VersionThreeDotO/BugsEstimations#expired-bugs|4]] || || -|| || 12|| || 6 || 5 ||
|| **Email first-time bug-reporters**\\A welcome message and guide to triaging process || [[VersionThreeDotO/BugsEstimations#email-first-time|5]] || || 4 || 8 || - || || 15|| - ||
|| **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" || || || 6 || || - || || 8 || - ||
|| **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 || || || - || || 8 || 6 || 19|| - ||
|| **Flip Incomplete to New**\\Automatically flip bugs from Incomplete when information is provided. || ND || || 20|| 6 || - || || - || 7 ||
|| **CSV bug lists**\\Offering a CSV export containing bug metadata for download through the web || || || - || || 4 || 2 || - || - ||
|| **Customizable search columns**\\Being able to specify what columns you'd like to see in the bug list || || || - || || 9 || 5 || - || - ||
|| **[[/BetterPrivacyWorkflow]]**\\Allow special users to submit private bugs, and make it clear what consequences result of marking a public bug private || [[VersionThreeDotO/BugsEstimations#better-privacy-workflow|7]] || || - || || - || 4 || - ||14 ||
|| **Proactive bug imports**\\Enabling complete syncs from plugin-enabled sites || || || 8 ||14 || - || || || - ||
|| **[[/CollectingBugStatistics]]**\\Pre-requisite for the triage report and useful to external report builders || [[VersionThreeDotO/BugsEstimations#collecting-bug-statistics|ND]] || || - || || - || || 11||13 ||
|| **[[/FixingIrrelevantComments]]**\\Marking and hiding irrelevant comments. See [[https://bugs.edge.launchpad.net/malone/+bug/220535|bug 220535]]. This is for admins only to start with. || [[VersionThreeDotO/BugsEstimations#deleting-comments|2]] || || -||10 || 15|| || || - ||
|| **[[/CaptureDistroSeriesWhenFilingBugs]]**\\UI to allow the user to say "I don't know/Hardy/Intrepid/..." || [[VersionThreeDotO/BugsEstimations#capture-distroseries|3]] || || - || 7 || - || || 18|| - ||
|| **[[https://bugs.edge.launchpad.net/malone/+bug/174443|Project group dupefinder support]]** || [[VersionThreeDotO/BugsEstimations#project-group-dupefinder|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 || || || - ||13 || 16|| ||   || - ||
|| **Triage throughput report**\\See [[https://blueprints.edge.launchpad.net/launchpad/+spec/qastats-bug-triage|Triaging QoS Report]] || || || 16|| || - || || 14|| - ||
|| **Import a remote bug UI**\\One-push importing and task-annotation from Debbugs & Bugzilla || || || 17||15 || - || || || - ||
|| **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 || || || - || || - || || 9 || - ||
|| **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 || || || - || || - || || 10|| - ||
|| **Code review UI**\\Allow code review of patch attachments, feature-parity with Bugzilla (shouldn't this be in codehosting?) || || || - || || 10|| || - || - ||
|| **Better package name UI guidance**\\If the user selects "don't know" then lead him to an explanation || || || - || || - || || 12|| - ||
|| **Duplicate bug watch workflow**\\When a bugwatch is linked to multiple bugs, notify/warn users (how? when?) || || || 12|| || - || || - || - ||
|| **Crash reporting**\\Provide a repository of crashes linked to bug reports, possibly integration with Breakpad? || || || 14|| || - || || || - ||
|| **Workload estimation**\\Story points/hours || || || -|| || - || || - ||15 ||
|| **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. || || || - || || - || || 16|| - ||
|| **Timebomb New bugs**\\After 6/N months, all New bugs become Incomplete || || || 19|| || - || || || - ||
|| **[[/BugFreezing]]**\\Marking a bug as frozen, disallowing new comments from non-bug-team-members || || || 21|| || - || || || - ||
|| **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. || || || - || || - || || - || - ||
Line 61: Line 74:


= New unsorted items =

|| **File bugs on packages in PPAs** || || || || || || || || || ||
|| HWDB: [[/StoryCards#correlate-hwdb-with-bug|Correlate hardware configurations with bug reports]] || || || || || || || || || ||

Priorities for the Bugs Team

Feature SP Released M T B S U L
Complete initial API export 2.2.1
Package-specific reporting guidelines
Bonus points for a syntax for including screenshots
5-6 2.2.1 5 11 - 1 -
MaloneMeToo I
Being able to say and record "this bug affects me to"
3 2.1.11 3 9 13 7 1
Parse HWDB info I
Parsing out USB/PCI IDs and BIOS fields.
2.1.11 - - 4 -
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 -
/CompleteActivityLog
Ensuring bug activity captures all bug changes
12 2.2.3 23 2 5 2 3
Bug Activity UI Interleaving
Displaying activity in the comments view
9 2.2.3 22 3 6 5
/TagDiscipline
Actually using OfficialBugTags for something!
8 2.2.3 25 4 11 3 2
Filebug-workflow improvements 2.2.4*
Inline editing of bug description 2.2.4*
Bug page remake 2.2.4*
Bug page Q&A 2.2.5*
MaloneMeToo II
Using the recorded information and display it as a kind of ''hotness''
3 2.2.5* 3 9 13 7 1
Duplicate-detection inside launchpad
Scavenge Launchpad bugs with similar contents to the bug displayed and easily mark dupes
3 2.2.5* 15 3 5 6
Sanitize targeting to series/milestones
Basically only use series tasks for backports
2.2.6*
Personal bug dashboard
Add screen and bug listings for managing your bugs
2.2.6*
Fix issues with bug nominations discussed at UDS
Bug 253597, bug 253600, bug 253608, bug 253612, bug 110195, bug 253610
11 1 -
Negated Tags in Searches
Allow searching for bugs with some tags, but without others
2 13 12 16 - 5
/IgnoreSubscriptionsRevenge
Unsubscribing implicit subscribers from specific bugs
6 - 5 - - -
Importing from tarballs
Making it easier for people to import project bugs into Launchpad for bug tracking
7 - - - 8
UI for submitting bugs upstream II
Using our Trac and Bugzilla plugins
2 - -
/ExplicitSearchFilteringAndCleanURLs
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 7 14 20 10
Status/Milestone updates for milestoned bugs
Simple UI to update selected bugs
20 10 2 1 - 11
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
ND 18 7 17 12
Quick summary/description/tags editing
Allowing people to change these fields without two pageloads. Estimated excluding AJAX
5 9 1 9
Expired bugs
Allowing us to track expired bugs separately from invalid, including a textual rationale
4 - 12 6 5
Email first-time bug-reporters
A welcome message and guide to triaging process
5 4 8 - 15 -
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"
6 - 8 -
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
- 8 6 19 -
Flip Incomplete to New
Automatically flip bugs from Incomplete when information is provided.
ND 20 6 - - 7
CSV bug lists
Offering a CSV export containing bug metadata for download through the web
- 4 2 - -
Customizable search columns
Being able to specify what columns you'd like to see in the bug list
- 9 5 - -
/BetterPrivacyWorkflow
Allow special users to submit private bugs, and make it clear what consequences result of marking a public bug private
7 - - 4 - 14
Proactive bug imports
Enabling complete syncs from plugin-enabled sites
8 14 - -
/CollectingBugStatistics
Pre-requisite for the triage report and useful to external report builders
ND - - 11 13
/FixingIrrelevantComments
Marking and hiding irrelevant comments. See bug 220535. This is for admins only to start with.
2 - 10 15 -
/CaptureDistroSeriesWhenFilingBugs
UI to allow the user to say "I don't know/Hardy/Intrepid/..."
3 - 7 - 18 -
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
- 13 16 -
Triage throughput report
See Triaging QoS Report
16 - 14 -
Import a remote bug UI
One-push importing and task-annotation from Debbugs & Bugzilla
17 15 - -
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
- - 9 -
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
- - 10 -
Code review UI
Allow code review of patch attachments, feature-parity with Bugzilla (shouldn't this be in codehosting?)
- 10 - -
Better package name UI guidance
If the user selects "don't know" then lead him to an explanation
- - 12 -
Duplicate bug watch workflow
When a bugwatch is linked to multiple bugs, notify/warn users (how? when?)
12 - - -
Crash reporting
Provide a repository of crashes linked to bug reports, possibly integration with Breakpad?
14 - -
Workload estimation
Story points/hours
- - - 15
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.
- - 16 -
Timebomb New bugs
After 6/N months, all New bugs become Incomplete
19 - -
/BugFreezing
Marking a bug as frozen, disallowing new comments from non-bug-team-members
21 - -
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.
- - - -

Contacts:

  • 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

Notes

  • 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.
  • Ubuntu:
  • 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.
  • MOTU:
  • also cited performance (cited 3-second page loads)
  • Auto-detecting threads related to bug reports
  • Bazaar:
  • Mass bug editing would be high on our list
  • Consider https://wiki.canonical.com/BazaarInfrastructureNeeds
  • Performance also cited

Bug tracker integration candidates

New suggestions

Specs or parts thereof

VersionThreeDotO/Bugs (last edited 2009-04-03 14:52:29 by bjornt)