id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
29	"Fix usability issue with limit_choices_to and ""Add another"" in admin"	Adrian Holovaty	nobody	"{{{
django34: We have the ability to put a customized limit/filter on which related objects get displayed in select boxes. For instance, the ""photographer"" field on the ""Add photo"" form only displays the ""Staff members"" that have shoots_photos=True.

django34: This results in some usability problems, though, because if a producer doesn't see a person's name in the list, he might click ""Add another..."" instead of checking to make sure the person isn't in ""Staff members"" and doesn't have ""shoots_photos"" checked.

django34: Does this make sense?

wilson: kind of

wilson: what page would that case appear on

django34: Here's an example...

django34: The ""Photographer"" select box includes *only* the staff members that have shoots_photos=True.

django34: So if a producer doesn't see a photographer in there, he might click ""Add another..."", which would create an entirely new staff member. But it might be the case that the staff member DOES exist, just doesn't have shoots_photos=True checked.

wilson: if the staff member did exist, would it let them add them again?

django34: Yes, as long as the slug was different.

django34: The only way I can think of to fix this would be to have some sort of ""Showing only photographers [Show all staff members]"" link. Or to eliminate the filtering altogether.

wilson: i was going to suggest a ""show all staff"" link

wilson: yes, that is my suggestion

wilson: ""show all staff"" link next to the select

wilson: then ""show photographers only"" when the filter is off

django34: All right.
}}}"	Bug	closed	contrib.admin	dev	Normal	wontfix		jamespic@…	Someday/Maybe	0	0	0	0	0	1