| 2005-07-10 03:33:28 |
Matthew Paul Thomas |
bug |
|
|
added bug |
| 2005-07-20 17:58:59 |
Brad Bollenbach |
malone: status |
New |
Accepted |
|
| 2005-07-20 17:58:59 |
Brad Bollenbach |
malone: assignee |
|
bradb |
|
| 2005-07-20 17:59:19 |
Brad Bollenbach |
malone: statusexplanation |
|
See also: https://launchpad.ubuntu.com/malone/bugs/1530 |
|
| 2005-07-20 20:26:45 |
Matthew Paul Thomas |
description |
Malone bug report pages currently feature an "+ Upstream" link to a page headed "Add Task to fix bug Upstream", an "+ In Distro" link to a page headed "Add SourcePackage Bug Task", and an "+ In Distro Release" link to a page headed "Add Distro Release Bug Task". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these three links should be merged into an "+ Also Want a Fix For..." link, to a page that's headed "Request fix for bug #123456". The page should list the places where a fix has already been requested, and let people request an additional fix in an upstream product or a distribution, with the option of specifying a release if they choose a distribution. As a combined page, it can contain any help text necessary for choosing between upstream, distributions, and distribution releases. |
Malone bug report pages currently feature an "+ Upstream" link to a page headed "Add Task to fix bug Upstream", an "+ In Distro" link to a page headed "Add SourcePackage Bug Task", and an "+ In Distro Release" link to a page headed "Add Distro Release Bug Task". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these three links should be merged into an "+ Also Want a Fix For..." link, to a page that's headed "Request fix for bug #123456". The page should list the places where a fix has already been requested, and let people request an additional fix in an upstream product or a distribution, with the option of specifying a release if they choose a distribution. As a combined page, it can contain any help text necessary for choosing between upstream, distributions, and distribution releases (fixing bug 1530 in the process). |
|
| 2005-07-20 20:27:13 |
Matthew Paul Thomas |
malone: statusexplanation |
See also: https://launchpad.ubuntu.com/malone/bugs/1530 |
|
|
| 2006-02-01 00:29:31 |
Matthew Paul Thomas |
summary |
Malone bug report pages currently feature an "+ Upstream" link to a page headed "Add Task to fix bug Upstream", an "+ In Distro" link to a page headed "Add SourcePackage Bug Task", and an "+ In Distro Release" link to a page headed "Add Distro Release Bug Task" |
|
|
| 2006-02-01 00:29:31 |
Matthew Paul Thomas |
description |
Malone bug report pages currently feature an "+ Upstream" link to a page headed "Add Task to fix bug Upstream", an "+ In Distro" link to a page headed "Add SourcePackage Bug Task", and an "+ In Distro Release" link to a page headed "Add Distro Release Bug Task". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these three links should be merged into an "+ Also Want a Fix For..." link, to a page that's headed "Request fix for bug #123456". The page should list the places where a fix has already been requested, and let people request an additional fix in an upstream product or a distribution, with the option of specifying a release if they choose a distribution. As a combined page, it can contain any help text necessary for choosing between upstream, distributions, and distribution releases (fixing bug 1530 in the process). |
Malone bug report pages currently feature an "+ Upstream..." link to a page headed "Request fix in a product", and an "+ In Distribution..." link to a page headed "Request fix in a distribution". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these three links should be merged into a "+ Request a fix elsewhere..." link, to a page that's headed "Request fix for bug #123456". The page should list the places where a fix has already been requested, and let people request an additional fix in an upstream product or a distribution, with the option of specifying a release if they choose a distribution. As a combined page, it can contain any help text necessary for choosing between upstream, distributions, and distribution releases (fixing bug 1530 in the process). |
|
| 2006-02-01 00:29:31 |
Matthew Paul Thomas |
title |
"Indicate bug also exists:" links should be merged |
"Request fix:" links should be merged into "Request a fix elsewhere..." |
|
| 2006-08-08 06:18:40 |
Matthew Paul Thomas |
description |
Malone bug report pages currently feature an "+ Upstream..." link to a page headed "Request fix in a product", and an "+ In Distribution..." link to a page headed "Request fix in a distribution". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these three links should be merged into a "+ Request a fix elsewhere..." link, to a page that's headed "Request fix for bug #123456". The page should list the places where a fix has already been requested, and let people request an additional fix in an upstream product or a distribution, with the option of specifying a release if they choose a distribution. As a combined page, it can contain any help text necessary for choosing between upstream, distributions, and distribution releases (fixing bug 1530 in the process). |
Malone bug report pages currently feature an "+ Upstream…" link to a page headed "Request fix in a product", and a "+ Distribution…" link to a page headed "Request fix in a distribution". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose. |
|
| 2006-08-08 06:18:40 |
Matthew Paul Thomas |
title |
"Request fix:" links should be merged into "Request a fix elsewhere..." |
"Also affects:" "Upstream…" and "Distribution…" links should be merged |
|
| 2006-08-18 14:59:55 |
Brad Bollenbach |
malone: assignee |
bradb |
|
|
| 2006-08-18 14:59:55 |
Brad Bollenbach |
malone: statusexplanation |
|
|
|
| 2007-08-29 22:28:10 |
Matthew Paul Thomas |
description |
Malone bug report pages currently feature an "+ Upstream…" link to a page headed "Request fix in a product", and a "+ Distribution…" link to a page headed "Request fix in a distribution". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose. |
Launchpad bug report pages currently feature a "+ Project…" link to a page headed "Record as affecting another project", and a "+ Distribution/Package…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself. |
|
| 2007-08-29 22:28:10 |
Matthew Paul Thomas |
title |
"Also affects:" "Upstream…" and "Distribution…" links should be merged |
"Also affects:" "Project…" and "Distribution/Package…" links should be merged |
|
| 2007-10-04 06:50:09 |
Matthew Paul Thomas |
malone: assignee |
|
mpt |
|
| 2007-11-14 01:07:39 |
Matthew Paul Thomas |
description |
Launchpad bug report pages currently feature a "+ Project…" link to a page headed "Record as affecting another project", and a "+ Distribution/Package…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself. |
Launchpad bug report pages currently feature a "+ Project…" link to a page headed "Record as affecting another project", and a "+ Distribution/Package…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 158732. |
|
| 2008-07-06 17:27:33 |
Matthew Paul Thomas |
description |
Launchpad bug report pages currently feature a "+ Project…" link to a page headed "Record as affecting another project", and a "+ Distribution/Package…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 158732. |
Launchpad bug report pages currently feature a "+ Project…" link to a page headed "Record as affecting another project", and a "+ Distribution/Package…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 117460 and bug 158732. |
|
| 2008-07-29 13:31:44 |
Matthew Paul Thomas |
description |
Launchpad bug report pages currently feature a "+ Project…" link to a page headed "Record as affecting another project", and a "+ Distribution/Package…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 117460 and bug 158732. |
Launchpad bug report pages currently feature a "+ Project…" link to a page headed "Record as affecting another project", and a "+ Distribution/Package…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 117460, bug 158732, and bug 244998. |
|
| 2008-10-20 12:45:59 |
Matthew Paul Thomas |
description |
Launchpad bug report pages currently feature a "+ Project…" link to a page headed "Record as affecting another project", and a "+ Distribution/Package…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 117460, bug 158732, and bug 244998. |
Launchpad bug report pages currently feature an "+ Also affects project…" link to a page headed "Record as affecting another project", and an "+ Also affects distribution…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
<https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2007-November/002451.html>
<https://lists.ubuntu.com/archives/ubuntu-server/2008-October/002319.html>
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 117460, bug 158732, and bug 244998. |
|
| 2008-11-06 15:39:40 |
Matthew Paul Thomas |
description |
Launchpad bug report pages currently feature an "+ Also affects project…" link to a page headed "Record as affecting another project", and an "+ Also affects distribution…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
<https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2007-November/002451.html>
<https://lists.ubuntu.com/archives/ubuntu-server/2008-October/002319.html>
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 117460, bug 158732, and bug 244998. |
Launchpad bug report pages currently feature an "+ Also affects project…" link to a page headed "Record as affecting another project", and an "+ Also affects distribution…" link to a page headed "Also affects distribution/package". People are unlikely to understand these, and especially unlikely to be able to choose the right option without reading an explanation of each.
<https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2007-November/002451.html>
<https://lists.ubuntu.com/archives/ubuntu-server/2008-October/002319.html>
Therefore, these two links should be merged, letting you choose on a single page whether the bug affects another product, distribution, or distribution package. This single page can contain text helping people understand which option to choose.
Ideally, this page would be an expandable section of the bug page itself.
It may save time to fix this bug at the same time as bug 117460, bug 158732, and bug 244998. Fixing this bug would also fix bug 294270. |
|
| 2011-04-26 22:40:54 |
Robert Collins |
summary |
"Also affects:" "Project…" and "Distribution/Package…" links should be merged |
Separate "also affects: " Project and Distribution links are hard to use and confusing |
|
| 2011-04-26 22:41:05 |
Robert Collins |
launchpad: assignee |
Matthew Paul Thomas (mpt) |
|
|
| 2011-04-26 22:41:07 |
Robert Collins |
launchpad: importance |
Medium |
Low |
|
| 2011-05-30 08:26:01 |
William Grant |
removed subscriber Canonical Launchpad Engineering |
|
|
|
| 2011-06-09 02:32:46 |
Curtis Hovey |
tags |
lp-bugs ui |
lp-bugs project-picker ui |
|
| 2011-07-18 10:45:22 |
Shriramana Sharma |
bug |
|
|
added subscriber Shriramana Sharma |
| 2011-08-02 15:07:41 |
Curtis Hovey |
launchpad: importance |
Low |
High |
|
| 2011-08-02 15:07:59 |
Curtis Hovey |
tags |
lp-bugs project-picker ui |
disclosure lp-bugs project-picker ui |
|
| 2011-08-02 19:35:41 |
Curtis Hovey |
tags |
disclosure lp-bugs project-picker ui |
disclosure lp-bugs target-picker ui |
|
| 2011-09-14 14:17:15 |
Curtis Hovey |
tags |
disclosure lp-bugs target-picker ui |
lp-bugs target-picker ui |
|
| 2011-10-11 14:48:35 |
Curtis Hovey |
launchpad: importance |
High |
Low |
|
| 2012-01-11 20:53:26 |
Zooko Wilcox-O'Hearn |
bug |
|
|
added subscriber Zooko Wilcox-O'Hearn |
| 2016-07-21 15:32:12 |
Colin Watson |
bug task added |
|
man-db (Ubuntu) |
|
| 2016-07-21 15:32:21 |
Colin Watson |
bug task deleted |
man-db (Ubuntu) |
|
|
