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
3455	"Documentation for ""choices"" should mention ""get_FOO_display"""	James Bennett	Jacob	"The documentation for the `choices` attribute on model fields mentions that `choices` should be a tuple of 2-tuples, including an actual value and a human-readable name, but documentation on how to retrieve the human-readable name of the selected choice from an instance of the model lives elsewhere, in the database API documentation, under the unintuitive name of `get_FOO_display`. This hinders a new user of Django trying to understand how best to make use of `choices`.

At the very least, the model documentation should include, under `choices`, a link to the `get_FOO_display` entry in the DB documentation for an explanation of how to get the human-readable name back out of a model instance. Ideally, we'd do that and come up with better titles for the sections on the various `get_FOO_display`/`get_next_by_FOO`/etc. methods."		closed	Documentation	dev		fixed	choices get_FOO_display		Ready for checkin	1	0	0	0	0	0