9453
Comment:
|
11378
|
Deletions are marked like this. | Additions are marked like this. |
Line 267: | Line 267: |
<<Anchor(activity-log-comment-interleaving)>> === Activity log interleaved with bug comments === {{{ As a bug triager, I want to see the most important changes to a bug interleaved with the comments, so that I don't have to reconcile information from two different pages in my head. }}} :: '''Story Points:''' :: '''Bug Tag:''' [[https://edge.launchpad.net/malone/+bugs?field.tag=story-activity-log-comment-interleaving|story-activity-log-comment-interleaving]] :: Notes * This is just interleaving the activity log items with the bug comments. It doesn't cover grouping together related changes and comments. <<Anchor(activity-log-group-changes)>> === Group together bug activty happening at the same time === {{{ As a bug triager, I want to see changes that happened at the same time as one unit, so that it's easier to see what other things the user was doing with the bug in the same interaction. }}} :: '''Story Points:''' :: '''Bug Tag:''' [[https://edge.launchpad.net/malone/+bugs?field.tag=story-activity-log-group-changes|story-activity-log-group-changes]] <<Anchor(optionally-show-all-activity-log-interleaved)>> === Optionally show all activity log items interleaved with comments === {{{ As a bug triager, I want to choose what information about the bug activity that is shown, so that I can concentrate on the changes that are most relevant to me right now. }}} :: '''Story Points:''' :: '''Bug Tag:''' [[https://edge.launchpad.net/malone/+bugs?field.tag=story-optionally-show-all-activity-log-interleaved|story-optionally-show-all-activity-log-interleaved]] :: Notes * By default we don't show all activity log items on the bug page itself, for example subscription events. By making it possible to optionally show them as well, we could get rid of the separate activity log page. |
Story cards for the Launchpad Bugs team.
Contents
HWDB
The Hardware Database is used to help triagers and developers to see which devices aren't working well, decide whether there are enough users with a device to warrant support, get more debug information, etc.
Get number of affected users by a bug tied to a device
As a kernel developer, I want to know how many users are using a certain PCI or USB device, so that I know how how well we need to support the device.
Story Points:
Bug Tag: story-hwdb-affected-users
- Notes
- Needs to be able to filter on distro series, since a bug fix may be needed in a stable series, if there are many users being affected by that bug using an older series.
Get number of users using a driver
As a kernel developer, I'd like to know how many users use device driver X so that I know how important bug fix backports are.
Story Points:
Bug Tag: story-hwdb-users-using-driver
- Notes
Include DMI and lspci information in HWDB submissions
As a kernel developer, I want to know the DMI and lspci data, so that I can easier debug a problem reported by a user.
Story Points:
Bug Tag: story-hwdb-dmi-lspci
- Notes
- Needs DMI and lspci data
- Access to raw submission via API OK
Find out which computers have a certain device
As a QA team member, I want to know which of the machines in our certification lab has device X installed, so that i can run tests with the most recent version of package Y.
Story Points:
- Notes
- How do you specify the set of computers you're interested in?
Correlate hardware configurations with bug reports
As a kernel developer, I want to see if a bug correlates with certain hardware configurations or drivers, so that I can get a better clue where to look for the cause of the bug.
Story Points:
Bug Tag:
- Notes
- Should the correlation be made by a human by looking from the HWDB submissions manually, or should it be done automatically somehow?
Upstreaming
Being able to forward and link bugs in Launchpad to upstream bug trackers is vital for Ubuntu. The stories here aim to improve that workflow, making it easier to connect bugs that have been reported in Launchpad to bugs in other bug trackers.
Link to file bugs upstream
As a bug triager, I want to follow a link from Launchpad to file a bug in the upstream bug tracker, so that I can forward a bug in LP upstream without having to copy and paste the description
Story Points:
Bug Tag: story-link-to-upstream-filebug
- Notes
- The links should point to the upstream's filebug page with the description and summary fields pre-filled.
- The user will need to have an account in the upstream bug tracker
- Having the link leave LP is OK
- The link should appear when adding an upstream task
Link to search bugs upstream
As a bug triager, I want to follow a link from Launchpad to search bugs in the upstream bug tracker, so that I can find possible duplicates upstream without having to copy and paste the summary of the bug in LP
Story Points:
Bug Tag: story-link-to-upstream-searchbugs
- Notes
- The link should perform a search using the bug summary
- Having the link leave LP is OK
- The link should appear when adding an upstream task
Enable search and filebug links for a project manually
As a project maintainer or bug triager, I want to set the remote product in the upstream bug tracker, so that users can easily search and file upstream bugs from Launchpad
Story Points:
Bug Tag: story-set-remote-product-manually
- Notes
- The triager doesn't have to be able to set it himself. He can file a question to have it done.
- This feature is useful for correcting links that are wrong.
Enable search and filebug links for a project automatically
As a bug triager, I want to get links for filing and searching bugs for projects where no one has set the remote product manually, so that I don't have to spend time updating all projects I'm interested in.
Story Points:
- Notes
- The script that does it should only set the remote product if it hasn't been set already.
AJAX
AJAX can be used in a number of locations to improve the workflows, and making pages quicker to load.
Inline editing of bug description and summary
As a bug triager, I want to edit both the summary and description inline, so that I don't have to wait for the page to load before starting to write the new text.
Story Points:
- Notes
- Most of the work will be done by the Foundations team.
- Should be finished at the AJAX sprint.
Activity log
Make sure that the bug activity log is complete. Sometimes we send only an e-mail when something changes about a bug, sometimes we only add it to the activity log, sometimes both, and sometimes we don't do anything. We've often chosen to do only one thing (like sending e-mail), and then simply forgot that we should add it to the activity log as well.
We need to change the API so that we won't forget to add things to the activity log, as well as fix the places where we currently don't add it to the activity log, even though we should.
Further more, we should improve the display of the activity log, so that it's interleaved with the bug comments.
Refactor activity log API
As a Launchpad developer, I want a single API for adding any kind of notification for a bug change, so that I won't forget to add something to the activity log
Story Points:
Bug Tag: sotry-refactor-activity-log-api
- Notes
- Refactor the API for indicating that something has change about the bug, so that the same API method is used for adding both e-mail notifications and items to the activity log. The API should be constructed so that the developer has to actively choose whether he should add it to the activity log.
Make future bugs' activity logs complete
As a bug triager, I want to see all changes to a bug in the activity log, so that I know what happened to it.
Story Points:
Bug Tag: story-future-activity-log-complete
- Notes
- We don't have to care much about filling in old activity events. We should talk to Ubuntu QA to see if there is any activity that they really want historical data for.
Activity log target identification
As a bug triager, I want to be able to identify which bug task each change in the activity log refers, so that the progress for each target is clear.
Story Points:
- Notes
- We currently have a lot of items when it's not clear which bug task's status changed.
- We might have to correct old data.
Activity log interleaved with bug comments
As a bug triager, I want to see the most important changes to a bug interleaved with the comments, so that I don't have to reconcile information from two different pages in my head.
Story Points:
- Notes
- This is just interleaving the activity log items with the bug comments. It doesn't cover grouping together related changes and comments.
Group together bug activty happening at the same time
As a bug triager, I want to see changes that happened at the same time as one unit, so that it's easier to see what other things the user was doing with the bug in the same interaction.
Story Points:
Bug Tag: story-activity-log-group-changes
Optionally show all activity log items interleaved with comments
As a bug triager, I want to choose what information about the bug activity that is shown, so that I can concentrate on the changes that are most relevant to me right now.
Story Points:
- Notes
- By default we don't show all activity log items on the bug page itself, for example subscription events. By making it possible to optionally show them as well, we could get rid of the separate activity log page.