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
28931	Non-conflicting `related_name` and `related_query_name` for `groups` and `user_permissions` columns in `PermissionsMixin`	Saiteja Parsi	Saiteja Parsi	"''AbstractUser'' extends ''PermissionsMixin'' to add the fields and methods necessary to support the ''Groups'' and ''Permission''. ''PermissionsMixin'' defines ''groups'' and ''user_permissions'' columns with many to many fields, both of which has a constant value for ''related_name'' and ''related_query_name' keys'. As ''AbstractUser'' inherit these fields, there is a high chance that these values raise conflicts when there are multiple classes inheriting from this abstract class, AbstractUser. So I suggest that instead of constant values for ''related_name'' and ''related_query_name' in ''PermissionsMixin', they should be dynamic values as described [https://docs.djangoproject.com/en/2.0/topics/db/models/#be-careful-with-related-name-and-related-query-name here].


"	Cleanup/optimization	closed	contrib.auth	2.0	Normal	wontfix	related_name, related_query_name, Abstract base classes, Model inheritance	saiteja.parsi@…	Unreviewed	1	0	0	0	0	0