Oops from changing bug's product when milestone is set
Bug #6026 reported by
Carlos Perelló Marín
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Brad Bollenbach |
Bug Description
Our UI allows us to change the product where the bug appears and at the same time, we can also change the milestone.
I know that the milestone is a field that depends on the product and that's why I think we should warn the user instead of having a system error (look at the today's OOPS-A357 for a trace).
Changed in malone: | |
assignee: | nobody → bradb |
status: | New → Accepted |
Changed in malone: | |
assignee: | bradb → nobody |
Changed in malone: | |
assignee: | nobody → bradb |
status: | Confirmed → In Progress |
Changed in malone: | |
status: | In Progress → Fix Committed |
Changed in malone: | |
status: | Fix Committed → Fix Released |
Changed in malone: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
On Wed, Dec 21, 2005 at 07:11:37PM -0000, Carlos Perelló Marín wrote:
> Our UI allows us to change the product where the bug appears and at the
> same time, we can also change the milestone.
>
> I know that the milestone is a field that depends on the product and
> that's why I think we should warn the user instead of having a system
> error (look at the today's OOPS-A357 for a trace).
This bug also occurs if you change the product of a bug that is already
assigned to a milestone.