Can't nominate a bug for an Ubuntu release when in a non-Ubuntu context
Bug #249434 reported by
Scott Kitterman
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Scott wrote:
"""
In bug 226891, I clicked on nominate for release and the only choice I get is 'Main'. Main is not a release. This completely breaks distro multiple release bug management. Thanks for improving Launchpad again.
"""
This is because he had ended up in the update-manager context. It should be possible to nominate a bug to an Ubuntu release, even if you're not in the bug's Ubuntu context. Having things depend on context like this leads to confusion.
Changed in launchpad: | |
importance: | Medium → Low |
To post a comment you must log in.
On Thu, Jul 17, 2008 at 12:05:41PM -0000, Scott Kitterman wrote:
> Public bug reported:
>
> In bug 226891, I clicked on nominate for release and the only choice I
> get is 'Main'. Main is not a release. This completely breaks distro
> multiple release bug management. Thanks for improving Launchpad again.
First of all, it's not totally broken. You can still nominate the bug
for a release, in the same way you've always nominated bugs. It has been
like this ever since we introduced nominations. This is not a
regression, we haven't changed anything here. If you are at this URL,
you should be able to nominate the bug for an Ubuntu release:
https:/ /launchpad. net/ubuntu/ +source/ amavisd- new/+bug/ 226891
That said, I'm not going to mark this bug as invalid, since there is /launchpad. net/bugs/ 226891, you should be able to nominate it for
clearly an issue here. Whether you can nominate something for a release
shouldn't depend in which context you'r in. If you go to
https:/
an Ubuntu release, no matter in which context you'll get redirected to.