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
13035	Wrong documentation for admin and default managers	rasca	Gabriel Hurley	"When creating custom models managers the docs say:

If you use custom Manager objects, take note that the first Manager Django encounters (in the order in which they're defined in the model) has a special status. Django interprets this first Manager defined in a class as the ""default"" Manager, and several parts of Django '''(though not the admin application)''' will use that Manager exclusively for that model. As a result, it's often a good idea to be careful in your choice of default manager, in order to avoid a situation where overriding of get_query_set() results in an inability to retrieve objects you'd like to work with.

So if in a model I have

{{{
new = NewManager()
objects = models.Manager()
}}}
the admin should work as if there isn't any NewManager but it doesn't

The following works as desired:
{{{
objects = models.Manager()
new = NewManager()
}}}"		closed	Documentation	dev		fixed	manager objects admin docs	rasca7@…	Accepted	1	0	0	0	0	0