| 2009-02-23 10:01:01 |
Matthew Paul Thomas |
bug |
|
|
added bug |
| 2009-02-23 10:20:51 |
Graham Binns |
malone: status |
New |
Triaged |
|
| 2009-02-23 10:20:51 |
Graham Binns |
malone: importance |
Undecided |
High |
|
| 2009-02-23 10:20:51 |
Graham Binns |
malone: statusexplanation |
|
Marking this as high since it has to potential, if fixed, to massively improve (or at least make it easier to improve) upstream linkages. |
|
| 2010-06-23 22:10:02 |
Bryce Harrington |
tags |
ubuntu-upstream-relations |
better-forwarding ubuntu-upstream-relations |
|
| 2010-08-19 00:56:58 |
Bryce Harrington |
attachment added |
|
must_link_watches.patch https://bugs.edge.launchpad.net/malone/+bug/333215/+attachment/1499145/+files/must_link_watches.patch |
|
| 2010-12-22 23:09:43 |
j.c.sackett |
bug |
|
|
added subscriber j.c.sackett |
| 2010-12-31 17:25:23 |
Curtis Hovey |
tags |
better-forwarding lp-bugs ubuntu-upstream-relations |
better-forwarding bugwatch lp-bugs ubuntu-upstream-relations |
|
| 2011-12-31 22:42:57 |
Robert Collins |
summary |
Bug affecting non-Launchpad-using project isn't advertised as needing linking |
Launchpad permits tasks to be added to projects that 'do not use launchpad for bug tracking' |
|
| 2011-12-31 22:44:40 |
Robert Collins |
description |
1. From an existing bug report, choose "Also affects project".
2. Choose a project that does not use Launchpad for bug tracking, e.g. Evolution.
What happens: Launchpad records the bug as affecting Evolution, and does nothing else.
What should happen: Launchpad should advertise, to anyone reading the bug report, that the next step in getting the bug fixed is to link it to the equivalent bug report in Gnome Bugzilla. |
1. From an existing bug report, choose "Also affects project".
2. Choose a project that does not use Launchpad for bug tracking, e.g. Evolution.
What happens: Launchpad records the bug as affecting Evolution, and does nothing else.
Diagnosis
=========
This results in unusable bug tasks, with no useful links to upstream or anything else.
Possible solutions
==================
* Simply prevent the task being added.
* Prevent it being added but open a tab/form/link to the upstream tracker
* Have a workflow which steps the user into the upstream tracker and then back again
* Have LP maintain credentials to file bugs in the upstream tracker programatically. |
|
| 2012-04-04 12:59:13 |
Curtis Hovey |
description |
1. From an existing bug report, choose "Also affects project".
2. Choose a project that does not use Launchpad for bug tracking, e.g. Evolution.
What happens: Launchpad records the bug as affecting Evolution, and does nothing else.
Diagnosis
=========
This results in unusable bug tasks, with no useful links to upstream or anything else.
Possible solutions
==================
* Simply prevent the task being added.
* Prevent it being added but open a tab/form/link to the upstream tracker
* Have a workflow which steps the user into the upstream tracker and then back again
* Have LP maintain credentials to file bugs in the upstream tracker programatically. |
1. From an existing bug report, choose "Also affects project".
2. Choose a project that does not use Launchpad for bug tracking, e.g. Evolution.
What happens: Launchpad records the bug as affecting Evolution, and does nothing else.
Diagnosis
=========
This results in unusable bug tasks, with no useful links to upstream or anything else.
Possible solutions
==================
* Simply prevent the task being added.
- affects project is using the wrong vocabulary. UsesBugsDistributionVocabulary illustrates how to make the correct vocabulary for projects.
* Prevent it being added but open a tab/form/link to the upstream tracker
* Have a workflow which steps the user into the upstream tracker and then back again
* Have LP maintain credentials to file bugs in the upstream tracker programatically. |
|
| 2012-07-25 10:37:03 |
Marius B. Kotsbak |
bug |
|
|
added subscriber Marius Kotsbak |
