| 2008-07-02 20:13:27 |
Scott Kitterman |
bug |
|
|
added bug |
| 2008-07-04 11:45:13 |
Matthew Paul Thomas |
launchpad: status |
New |
Confirmed |
|
| 2008-07-04 11:45:13 |
Matthew Paul Thomas |
launchpad: importance |
Undecided |
High |
|
| 2008-07-04 11:47:01 |
Matthew Paul Thomas |
description |
Times are -0400 and the log is from #ubuntu-devel.
[15:54] <maix> > So far it's not been requested. It would have to be requested (use also
[15:54] <maix> > affects to add gutsy-backports) and them tested on gutsy.
[15:54] <maix> (https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/223789)
[15:54] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:54] <maix> i cannot find such a link/option there
[15:55] <ScottK> See where it says "Also affects project" right under mercurial(ubuntu)?
[15:55] <ScottK> Click on that.
[15:55] <maix> yes?
[15:55] <maix> (i've tried that but it did not seem to be the right thing to me :)
[15:56] --> Spads has joined this channel (n=spacehob@unaffiliated/spads).
[15:56] --> imbrandon has joined this channel (n=bholtscl@ubuntu/member/pdpc.active.imbrandon).
[15:56] <ScottK> Yes. Actually you need to do that from https://bugs.launchpad.net/hardy-backports/+bug/223789
[15:56] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:57] <ScottK> Then when it asks you about the affected project say gutsy-backports.
[15:58] <ScottK> maix: Does that work better?
[15:58] <maix> yes
[15:59] <ScottK> Feel free to discuss the user-friendly U/I in #launchpad. My thoughts on the matter are well known.
[15:59] <maix> but that's very confusing, why are there completely different options if i access the same bug by a different url
[15:59] <ScottK> That's a good question to ask in #launchpad.
[16:00] <maix> ok then i can guess what your thougts are :)
The only way I could find to get to the hardy-backports URL from the ubuntu/+source/mercurial URL was to hand type it in and there was not a way to add the package to gutsy-backports from the ubuntu/+source/mercurial URL.
Something less opaque would be nice. |
Times are -0400 and the log is from #ubuntu-devel.
[15:54] <maix> > So far it's not been requested. It would have to be requested (use also
[15:54] <maix> > affects to add gutsy-backports) and them tested on gutsy.
[15:54] <maix> (https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/223789)
[15:54] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:54] <maix> i cannot find such a link/option there
[15:55] <ScottK> See where it says "Also affects project" right under mercurial(ubuntu)?
[15:55] <ScottK> Click on that.
[15:55] <maix> yes?
[15:55] <maix> (i've tried that but it did not seem to be the right thing to me :)
...
[15:56] <ScottK> Yes. Actually you need to do that from https://bugs.launchpad.net/hardy-backports/+bug/223789
[15:56] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:57] <ScottK> Then when it asks you about the affected project say gutsy-backports.
[15:58] <ScottK> maix: Does that work better?
[15:58] <maix> yes
[15:59] <ScottK> Feel free to discuss the user-friendly U/I in #launchpad. My thoughts on the matter are well known.
[15:59] <maix> but that's very confusing, why are there completely different options if i access the same bug by a different url
[15:59] <ScottK> That's a good question to ask in #launchpad.
[16:00] <maix> ok then i can guess what your thougts are :)
The only way I could find to get to the hardy-backports URL from the ubuntu/+source/mercurial URL was to hand type it in and there was not a way to add the package to gutsy-backports from the ubuntu/+source/mercurial URL.
Something less opaque would be nice. |
|
| 2008-07-04 11:47:01 |
Matthew Paul Thomas |
title |
No apparent way to report bug affecting another project |
"Also affects project" disallows adding a project depending on context |
|
| 2008-07-04 13:54:14 |
Björn Tillenius |
bug |
|
|
added subscriber Björn Tillenius |
| 2008-07-07 09:28:15 |
Matthew Paul Thomas |
description |
Times are -0400 and the log is from #ubuntu-devel.
[15:54] <maix> > So far it's not been requested. It would have to be requested (use also
[15:54] <maix> > affects to add gutsy-backports) and them tested on gutsy.
[15:54] <maix> (https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/223789)
[15:54] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:54] <maix> i cannot find such a link/option there
[15:55] <ScottK> See where it says "Also affects project" right under mercurial(ubuntu)?
[15:55] <ScottK> Click on that.
[15:55] <maix> yes?
[15:55] <maix> (i've tried that but it did not seem to be the right thing to me :)
...
[15:56] <ScottK> Yes. Actually you need to do that from https://bugs.launchpad.net/hardy-backports/+bug/223789
[15:56] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:57] <ScottK> Then when it asks you about the affected project say gutsy-backports.
[15:58] <ScottK> maix: Does that work better?
[15:58] <maix> yes
[15:59] <ScottK> Feel free to discuss the user-friendly U/I in #launchpad. My thoughts on the matter are well known.
[15:59] <maix> but that's very confusing, why are there completely different options if i access the same bug by a different url
[15:59] <ScottK> That's a good question to ask in #launchpad.
[16:00] <maix> ok then i can guess what your thougts are :)
The only way I could find to get to the hardy-backports URL from the ubuntu/+source/mercurial URL was to hand type it in and there was not a way to add the package to gutsy-backports from the ubuntu/+source/mercurial URL.
Something less opaque would be nice. |
1. From <https://staging.launchpad.net/ubuntu/+source/mercurial/+bug/223789>, try to record the bug as needing to be fixed in the "edgy-backports" project.
What happens: When you click "Also affects project", the resulting page <https://bugs.staging.launchpad.net/ubuntu/+source/mercurial/+bug/223789/+choose-affected-product> is completely different from the usual one (that you would get, for example, from <https://bugs.staging.launchpad.net/hardy-backports/+bug/223789>). Because people naturally look at the form fields first, skipping over any non-form text, it is very difficult to find how to specify a different project.
What should happen: The "Also affects project" link should display the same form regardless of context. Suggested upstreams should be radio buttons added to the usual form, rather than a completely different form.
From #ubuntu-devel:
[15:54] <maix> > So far it's not been requested. It would have to be requested (use also
[15:54] <maix> > affects to add gutsy-backports) and them tested on gutsy.
[15:54] <maix> (https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/223789)
[15:54] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:54] <maix> i cannot find such a link/option there
[15:55] <ScottK> See where it says "Also affects project" right under mercurial(ubuntu)?
[15:55] <ScottK> Click on that.
[15:55] <maix> yes?
[15:55] <maix> (i've tried that but it did not seem to be the right thing to me :)
...
[15:56] <ScottK> Yes. Actually you need to do that from https://bugs.launchpad.net/hardy-backports/+bug/223789
[15:56] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:57] <ScottK> Then when it asks you about the affected project say gutsy-backports.
[15:58] <ScottK> maix: Does that work better?
[15:58] <maix> yes
[15:59] <ScottK> Feel free to discuss the user-friendly U/I in #launchpad. My thoughts on the matter are well known.
[15:59] <maix> but that's very confusing, why are there completely different options if i access the same bug by a different url
[15:59] <ScottK> That's a good question to ask in #launchpad.
[16:00] <maix> ok then i can guess what your thougts are :)
The only way I could find to get to the hardy-backports URL from the ubuntu/+source/mercurial URL was to hand type it in and there was not a way to add the package to gutsy-backports from the ubuntu/+source/mercurial URL.
Something less opaque would be nice. |
|
| 2008-07-07 09:28:15 |
Matthew Paul Thomas |
title |
"Also affects project" disallows adding a project depending on context |
"Also affects project" is inconsistent and obscure when in package context |
|
| 2008-07-29 13:32:12 |
Matthew Paul Thomas |
description |
1. From <https://staging.launchpad.net/ubuntu/+source/mercurial/+bug/223789>, try to record the bug as needing to be fixed in the "edgy-backports" project.
What happens: When you click "Also affects project", the resulting page <https://bugs.staging.launchpad.net/ubuntu/+source/mercurial/+bug/223789/+choose-affected-product> is completely different from the usual one (that you would get, for example, from <https://bugs.staging.launchpad.net/hardy-backports/+bug/223789>). Because people naturally look at the form fields first, skipping over any non-form text, it is very difficult to find how to specify a different project.
What should happen: The "Also affects project" link should display the same form regardless of context. Suggested upstreams should be radio buttons added to the usual form, rather than a completely different form.
From #ubuntu-devel:
[15:54] <maix> > So far it's not been requested. It would have to be requested (use also
[15:54] <maix> > affects to add gutsy-backports) and them tested on gutsy.
[15:54] <maix> (https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/223789)
[15:54] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:54] <maix> i cannot find such a link/option there
[15:55] <ScottK> See where it says "Also affects project" right under mercurial(ubuntu)?
[15:55] <ScottK> Click on that.
[15:55] <maix> yes?
[15:55] <maix> (i've tried that but it did not seem to be the right thing to me :)
...
[15:56] <ScottK> Yes. Actually you need to do that from https://bugs.launchpad.net/hardy-backports/+bug/223789
[15:56] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:57] <ScottK> Then when it asks you about the affected project say gutsy-backports.
[15:58] <ScottK> maix: Does that work better?
[15:58] <maix> yes
[15:59] <ScottK> Feel free to discuss the user-friendly U/I in #launchpad. My thoughts on the matter are well known.
[15:59] <maix> but that's very confusing, why are there completely different options if i access the same bug by a different url
[15:59] <ScottK> That's a good question to ask in #launchpad.
[16:00] <maix> ok then i can guess what your thougts are :)
The only way I could find to get to the hardy-backports URL from the ubuntu/+source/mercurial URL was to hand type it in and there was not a way to add the package to gutsy-backports from the ubuntu/+source/mercurial URL.
Something less opaque would be nice. |
1. From <https://staging.launchpad.net/ubuntu/+source/mercurial/+bug/223789>, try to record the bug as needing to be fixed in the "edgy-backports" project.
What happens: When you click "Also affects project", the resulting page <https://bugs.staging.launchpad.net/ubuntu/+source/mercurial/+bug/223789/+choose-affected-product> is completely different from the usual one (that you would get, for example, from <https://bugs.staging.launchpad.net/hardy-backports/+bug/223789>). Because people naturally look at the form fields first, skipping over any non-form text, it is very difficult to find how to specify a different project.
What should happen: The "Also affects project" link should display the same form regardless of context. Suggested upstreams should be radio buttons added to the usual form, rather than a completely different form.
From #ubuntu-devel:
[15:54] <maix> > So far it's not been requested. It would have to be requested (use also
[15:54] <maix> > affects to add gutsy-backports) and them tested on gutsy.
[15:54] <maix> (https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/223789)
[15:54] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:54] <maix> i cannot find such a link/option there
[15:55] <ScottK> See where it says "Also affects project" right under mercurial(ubuntu)?
[15:55] <ScottK> Click on that.
[15:55] <maix> yes?
[15:55] <maix> (i've tried that but it did not seem to be the right thing to me :)
...
[15:56] <ScottK> Yes. Actually you need to do that from https://bugs.launchpad.net/hardy-backports/+bug/223789
[15:56] <ubottu> Launchpad bug 223789 in hardy-backports "Please backport mercurial 1.0.1-2 from Intrepid to Hardy" [Wishlist,In progress]
[15:57] <ScottK> Then when it asks you about the affected project say gutsy-backports.
[15:58] <ScottK> maix: Does that work better?
[15:58] <maix> yes
[15:59] <ScottK> Feel free to discuss the user-friendly U/I in #launchpad. My thoughts on the matter are well known.
[15:59] <maix> but that's very confusing, why are there completely different options if i access the same bug by a different url
[15:59] <ScottK> That's a good question to ask in #launchpad.
[16:00] <maix> ok then i can guess what your thougts are :)
The only way I could find to get to the hardy-backports URL from the ubuntu/+source/mercurial URL was to hand type it in and there was not a way to add the package to gutsy-backports from the ubuntu/+source/mercurial URL.
Something less opaque would be nice.
(See also bug 1334.) |
|
| 2010-11-19 04:03:14 |
Robert Collins |
tags |
confusing-ui motu |
bridging-the-gap confusing-ui motu |
|
| 2010-11-30 14:55:36 |
Curtis Hovey |
tags |
bridging-the-gap confusing-ui motu |
confusing-ui motu |
|
