Assigning bug to someone else, without saying who, produces no warning

Bug #111937 reported by Matthew Paul Thomas
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

1. Open a bug page where you have permission to assign the bug.
2. In the "Assigned to:" section, click the radio button next to the person field, but leave the field blank.
3. Click "Save Changes".

What happens: The bug is deassigned.
What should happen: "/!\ You didn't enter a new assignee, so the assignee has not been changed."

Tags: lp-bugs ui
Revision history for this message
Jonathan Lange (jml) wrote :

This confused me a little until I noticed that bugs are deassigned by selecting the "Nobody" radio option.

Changed in malone:
status: Unconfirmed → Confirmed
Curtis Hovey (sinzui)
Changed in malone:
importance: Undecided → Low
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.