| 2010-05-29 18:55:17 |
Tomasz Chrzczonowicz |
bug |
|
|
added bug |
| 2010-05-29 19:39:09 |
Graham Binns |
malone: status |
New |
Triaged |
|
| 2010-05-29 19:39:12 |
Graham Binns |
malone: importance |
Undecided |
Medium |
|
| 2010-05-29 19:39:18 |
Graham Binns |
tags |
enhancement |
bugwatch enhancement |
|
| 2010-06-23 22:55:53 |
Bryce Harrington |
tags |
bugwatch enhancement |
better-forwarding bugwatch enhancement |
|
| 2010-06-23 22:59:48 |
Bryce Harrington |
description |
===The Problem===
The current process of forwarding bugs upstream:
1. Read https://wiki.ubuntu.com/Bugs/Upstream, if you haven't already.
2. Read https://wiki.ubuntu.com/Bugs/Watches, if you haven't already.
3. Report bug on Launchpad.
4. Search for upstream bug tracker for matching bugs.
5. Set up an account on the upstream bug tracker, if you haven't already.
6. Log into upstream bug tracker.
7. Create a new upstream bug report
8. Copy and paste the description from Launchpad
9. Copy and paste a link to the Launchpad report in the bug description and/or in some form field
10. Switch back to Launchpad, click "Also Affects Project" and copy and paste the upstream bug URL into Remote Watch field.
Results:
1. Takes more time that it could and should
2. Isn't easily discoverable
3. So people don't and won't do that.
From https://wiki.ubuntu.com/Bugs/Upstream :
Bugs that need forwarding to the Upstream bugtrackers:
https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=pending_bugwatch&field.status_upstream-empty-marker=1
Unlinked upstream bugs - Sometimes people add a link to an upstream bug tracker in the comments of a bug but don't bother creating an upstream task. This is a list of possible targets that can be linked. (Lots of low hanging fruit in this list, but also a bunch of dupes and ones inappropriate to be linked.) : http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html
===Solution===
The process could have only 3 steps:
1. After you report/triage a bug for an Ubuntu package in Launchpad, there is a button in the "What Next" section that says "Push Upstream!" or "Forward Upstream!"
2. Search results for your bug title are pulled from upstream bug tracker and slide out or pop up in a window, so you can check if it was already reported (Something like what your already have when reporting bugs in Launchpad). It has two buttons:
*New Report - you press it, when there is clearly nothing like your bug reported upstream.
*Link Reports - when there is an upstream report for your bug, but it's not watched in Launchpad. You pick one/several using a radio button/checkboxes.
3. Upstream Bug Tracker Authentication. One of the three:
[WORST] You're taken to the upstream bug tracker login page to enter your credentials. You need an upstream bug tracker account.
[SLIGHTLY BETTER] You're taken to your Launchpad/Ubuntu SSO OpenID authentication page if upstream bug tracker accepts OpenID.
[BEST] Launchpad has a its own upstream bug tracker account, say upstream-bugs@launchpad.net and uses that automagically, so you don't have to create your own account.
At this point, Launchpad could take care of the rest in fully automated manner. I.e:
1. It creates an upstream bug report,
2. Links it to one in Launchpad
3. Sets up watching it from Launchpad.
4. Maybe adds Launchpad bug subscribers to CC list of upstream bug report.
Obvious tasks:
1. Mappings from Ubuntu packages to upstream bug tracker components. But it only needs to be done once and currently users have to do it individually each time they forward the bug.
2. Scripts to query/search upstream bug trackers for duplicate/linkable bug reports. |
===The Problem===
The current process of forwarding bugs upstream:
1. Read https://wiki.ubuntu.com/Bugs/Upstream, if you haven't already.
2. Read https://wiki.ubuntu.com/Bugs/Watches, if you haven't already.
3. Report bug on Launchpad.
4. Search for upstream bug tracker for matching bugs.
5. Set up an account on the upstream bug tracker, if you haven't already.
6. Log into upstream bug tracker.
7. Create a new upstream bug report
8. Copy and paste the description from Launchpad
9. Copy and paste a link to the Launchpad report in the bug description and/or in some form field
10. Switch back to Launchpad, click "Also Affects Project" and copy and paste the upstream bug URL into Remote Watch field.
Results:
1. Takes more time that it could and should
2. Isn't easily discoverable
3. So people don't and won't do that.
From https://wiki.ubuntu.com/Bugs/Upstream :
Bugs that need forwarding to the Upstream bugtrackers:
https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=pending_bugwatch&field.status_upstream-empty-marker=1
Unlinked upstream bugs - Sometimes people add a link to an upstream bug tracker in the comments of a bug but don't bother creating an upstream task. This is a list of possible targets that can be linked. (Lots of low hanging fruit in this list, but also a bunch of dupes and ones inappropriate to be linked.) : http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html [This particular aspect of the problem is already covered in bug #333215 and/or bug #420353]
===Solution===
The process could have only 3 steps:
1. After you report/triage a bug for an Ubuntu package in Launchpad, there is a button in the "What Next" section that says "Push Upstream!" or "Forward Upstream!"
2. Search results for your bug title are pulled from upstream bug tracker and slide out or pop up in a window, so you can check if it was already reported (Something like what your already have when reporting bugs in Launchpad). It has two buttons:
*New Report - you press it, when there is clearly nothing like your bug reported upstream.
*Link Reports - when there is an upstream report for your bug, but it's not watched in Launchpad. You pick one/several using a radio button/checkboxes.
3. Upstream Bug Tracker Authentication. One of the three:
[WORST] You're taken to the upstream bug tracker login page to enter your credentials. You need an upstream bug tracker account.
[SLIGHTLY BETTER] You're taken to your Launchpad/Ubuntu SSO OpenID authentication page if upstream bug tracker accepts OpenID.
[BEST] Launchpad has a its own upstream bug tracker account, say upstream-bugs@launchpad.net and uses that automagically, so you don't have to create your own account.
At this point, Launchpad could take care of the rest in fully automated manner. I.e:
1. It creates an upstream bug report,
2. Links it to one in Launchpad
3. Sets up watching it from Launchpad.
4. Maybe adds Launchpad bug subscribers to CC list of upstream bug report.
Obvious tasks:
1. Mappings from Ubuntu packages to upstream bug tracker components. But it only needs to be done once and currently users have to do it individually each time they forward the bug.
2. Scripts to query/search upstream bug trackers for duplicate/linkable bug reports.
|
|
| 2010-08-19 21:36:25 |
Bryce Harrington |
description |
===The Problem===
The current process of forwarding bugs upstream:
1. Read https://wiki.ubuntu.com/Bugs/Upstream, if you haven't already.
2. Read https://wiki.ubuntu.com/Bugs/Watches, if you haven't already.
3. Report bug on Launchpad.
4. Search for upstream bug tracker for matching bugs.
5. Set up an account on the upstream bug tracker, if you haven't already.
6. Log into upstream bug tracker.
7. Create a new upstream bug report
8. Copy and paste the description from Launchpad
9. Copy and paste a link to the Launchpad report in the bug description and/or in some form field
10. Switch back to Launchpad, click "Also Affects Project" and copy and paste the upstream bug URL into Remote Watch field.
Results:
1. Takes more time that it could and should
2. Isn't easily discoverable
3. So people don't and won't do that.
From https://wiki.ubuntu.com/Bugs/Upstream :
Bugs that need forwarding to the Upstream bugtrackers:
https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=pending_bugwatch&field.status_upstream-empty-marker=1
Unlinked upstream bugs - Sometimes people add a link to an upstream bug tracker in the comments of a bug but don't bother creating an upstream task. This is a list of possible targets that can be linked. (Lots of low hanging fruit in this list, but also a bunch of dupes and ones inappropriate to be linked.) : http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html [This particular aspect of the problem is already covered in bug #333215 and/or bug #420353]
===Solution===
The process could have only 3 steps:
1. After you report/triage a bug for an Ubuntu package in Launchpad, there is a button in the "What Next" section that says "Push Upstream!" or "Forward Upstream!"
2. Search results for your bug title are pulled from upstream bug tracker and slide out or pop up in a window, so you can check if it was already reported (Something like what your already have when reporting bugs in Launchpad). It has two buttons:
*New Report - you press it, when there is clearly nothing like your bug reported upstream.
*Link Reports - when there is an upstream report for your bug, but it's not watched in Launchpad. You pick one/several using a radio button/checkboxes.
3. Upstream Bug Tracker Authentication. One of the three:
[WORST] You're taken to the upstream bug tracker login page to enter your credentials. You need an upstream bug tracker account.
[SLIGHTLY BETTER] You're taken to your Launchpad/Ubuntu SSO OpenID authentication page if upstream bug tracker accepts OpenID.
[BEST] Launchpad has a its own upstream bug tracker account, say upstream-bugs@launchpad.net and uses that automagically, so you don't have to create your own account.
At this point, Launchpad could take care of the rest in fully automated manner. I.e:
1. It creates an upstream bug report,
2. Links it to one in Launchpad
3. Sets up watching it from Launchpad.
4. Maybe adds Launchpad bug subscribers to CC list of upstream bug report.
Obvious tasks:
1. Mappings from Ubuntu packages to upstream bug tracker components. But it only needs to be done once and currently users have to do it individually each time they forward the bug.
2. Scripts to query/search upstream bug trackers for duplicate/linkable bug reports.
|
===The Problem===
The current process of forwarding bugs upstream:
1. Read https://wiki.ubuntu.com/Bugs/Upstream, if you haven't already.
2. Read https://wiki.ubuntu.com/Bugs/Watches, if you haven't already.
3. Report bug on Launchpad.
4. Search for upstream bug tracker for matching bugs.
5. Set up an account on the upstream bug tracker, if you haven't already.
6. Log into upstream bug tracker.
7. Create a new upstream bug report
8. Copy and paste the description from Launchpad
9. Copy and paste a link to the Launchpad report in the bug description and/or in some form field
10. Switch back to Launchpad, click "Also Affects Project" and copy and paste the upstream bug URL into Remote Watch field.
11. Download attachments worth including in the upstream report
12. For each attachment, attach it to the bugzilla report
13. Write a comment to the user that their report has been sent upstream. (If you're forwarding someone else's bug)
14. Mark the bug's status and importance as appropriate
Results:
1. Takes more time that it could and should
2. Isn't easily discoverable
3. So people don't and won't do that.
From https://wiki.ubuntu.com/Bugs/Upstream :
Bugs that need forwarding to the Upstream bugtrackers:
https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream=pending_bugwatch&field.status_upstream-empty-marker=1
Unlinked upstream bugs - Sometimes people add a link to an upstream bug tracker in the comments of a bug but don't bother creating an upstream task. This is a list of possible targets that can be linked. (Lots of low hanging fruit in this list, but also a bunch of dupes and ones inappropriate to be linked.) : http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html [This particular aspect of the problem is already covered in bug #333215 and/or bug #420353]
===Solution===
The process could have only 3 steps:
1. After you report/triage a bug for an Ubuntu package in Launchpad, there is a button in the "What Next" section that says "Push Upstream!" or "Forward Upstream!"
2. Search results for your bug title are pulled from upstream bug tracker and slide out or pop up in a window, so you can check if it was already reported (Something like what your already have when reporting bugs in Launchpad). It has two buttons:
*New Report - you press it, when there is clearly nothing like your bug reported upstream.
*Link Reports - when there is an upstream report for your bug, but it's not watched in Launchpad. You pick one/several using a radio button/checkboxes.
3. Upstream Bug Tracker Authentication. One of the three:
[WORST] You're taken to the upstream bug tracker login page to enter your credentials. You need an upstream bug tracker account.
[SLIGHTLY BETTER] You're taken to your Launchpad/Ubuntu SSO OpenID authentication page if upstream bug tracker accepts OpenID.
[BEST] Launchpad has a its own upstream bug tracker account, say upstream-bugs@launchpad.net and uses that automagically, so you don't have to create your own account.
At this point, Launchpad could take care of the rest in fully automated manner. I.e:
1. It creates an upstream bug report,
2. Links it to one in Launchpad
3. Sets up watching it from Launchpad.
4. Maybe adds Launchpad bug subscribers to CC list of upstream bug report.
Obvious tasks:
1. Mappings from Ubuntu packages to upstream bug tracker components. But it only needs to be done once and currently users have to do it individually each time they forward the bug.
2. Scripts to query/search upstream bug trackers for duplicate/linkable bug reports.
|
|
| 2011-02-02 20:51:16 |
Robert Collins |
launchpad: importance |
Medium |
Low |
|
| 2012-07-25 10:31:34 |
Marius B. Kotsbak |
bug |
|
|
added subscriber Marius Kotsbak |
| 2013-06-02 15:02:06 |
papukaija |
bug |
|
|
added subscriber papukaija |
