"Constraint not satisfied" error when assigning bug to someone else
Bug #602428 reported by
Martin Packman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When trying to assign bug 601466 to jelmer via +editstatus (javascript is disabled), launchpad rejected the change with "There is 1 error in the data you entered. Please fix it and try again", and "Constraint not satisfied" round the 'Assigned to' text input field. I am not in a group with admin rights to the bzr-pipeline project.
Tried the same thing on production rather than edge a few minutes later, and it worked fine.
Revision history for this message
| Deryck Hodge (deryck) wrote | #1 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: error-handling errors form-validation ui |
To post a comment you must log in.
Hi, thanks for reporting this bug. Clearly, our form validation needs to return a better error here. The behavior is expected now, though, since we changed our assignment code to only allow bug supervisors for a project to assign bugs to other people. However, this will be a very low priority for us to fix, since the majority of users never see this page by using the JavaScript widget on the bug page itself.
Cheers,
deryck