| 2008-11-21 13:58:38 |
Graham Binns |
bug |
|
|
added bug |
| 2008-11-21 13:59:53 |
Graham Binns |
malone: status |
New |
Triaged |
|
| 2008-11-21 13:59:53 |
Graham Binns |
malone: importance |
Undecided |
High |
|
| 2008-11-21 13:59:53 |
Graham Binns |
malone: statusexplanation |
|
|
|
| 2008-11-21 13:59:53 |
Graham Binns |
malone: milestone |
|
2.1.12 |
|
| 2008-12-05 07:44:46 |
Graham Binns |
malone: status |
Triaged |
In Progress |
|
| 2008-12-05 07:44:46 |
Graham Binns |
malone: assignee |
|
gmb |
|
| 2008-12-17 16:42:05 |
Graham Binns |
malone: statusexplanation |
|
Didn't land this cycle due to UDS and test failures. |
|
| 2008-12-17 16:42:05 |
Graham Binns |
malone: milestone |
2.1.12 |
2.2.1 |
|
| 2009-01-20 10:08:16 |
Graham Binns |
description |
At the moment we make no attempt to record the ID of a Product on a remote bug tracker when we link a Product to that bug tracker. This isn't usually a problem, since we import bug statuses by remote bug ID rather than remote project name / ID.
As start providing links to upstream bug-filing forms, however, we need to know the ID or name of the project on the remote bug tracker so that we can direct people to the right form.
Examples of this:
* For Bugzilla, we need to know the product name for the remote Bugzilla (e.g. http://bugzilla.example.com/enter_bug.cgi?product=Fronobulator).
* For SourceForge we need to know the product's GroupID and ATID.
For other bug trackers this may not be so important (for example in Trac the project name is part of the root URL, e.g. http://trac.example.com/myproject/newticket). |
At the moment we make no attempt to record the ID of a Product on a remote bug tracker when we link a Product to that bug tracker. This isn't usually a problem, since we import bug statuses by remote bug ID rather than remote project name / ID.
As start providing links to upstream bug-filing forms, however, we need to know the ID or name of the project on the remote bug tracker so that we can direct people to the right form.
Examples of this:
* For Bugzilla, we need to know the product name for the remote Bugzilla (e.g. http://bugzilla.example.com/enter_bug.cgi?product=Fronobulator).
* For SourceForge we need to know the product's GroupID and ATID.
For other bug trackers this may not be so important (for example in Trac the project name is part of the root URL, e.g. http://trac.example.com/myproject/newticket).
We will know this bug is fixed when:
* The remote product of a Product is accessible as an attribute of that product
* The remote product of a Product can be set using the Launchpad API |
|
| 2009-01-20 10:08:16 |
Graham Binns |
title |
If a Product is linked to a remote bug tracker the ID of the product on that remote tracker should be recorded |
Add infrastructure for recording the remote product for a Launchpad Product |
|
| 2009-01-20 10:09:06 |
Graham Binns |
title |
Add infrastructure for recording the remote product for a Launchpad Product |
Add infrastructure for recording the remote product for a project |
|
| 2009-01-23 10:28:17 |
Graham Binns |
malone: status |
In Progress |
Fix Committed |
|
| 2009-01-23 10:28:17 |
Graham Binns |
malone: statusexplanation |
Didn't land this cycle due to UDS and test failures. |
Landed in r7631. |
|
| 2009-01-29 09:00:40 |
Graham Binns |
malone: status |
Fix Committed |
Fix Released |
|
| 2009-01-29 09:00:40 |
Graham Binns |
malone: statusexplanation |
Landed in r7631. |
|
|
