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
23034	"Add migrations support for adding ManyToMany ""through"" model"	lorinkoz@…		"Adding a ""through"" model on a ManyToMany field make ""makemigrations"" fail with an explicit error stating that it is not possible. I have worked it around by renaming the field, creating the migration (so as to make Django believe it's a new field) and then renaming the field back to the original name and creating another migration (which is correctly acknowledged by Django as a simple ""renaming""). I understand the implications of adding a through model from the migrations perspective, but maybe a more friendly output could be achieved. Is it even possible to create some sort of interaction, like when you create a field with not null and no default value, so as to ask the user if they want to destroy/create a new field??"	New feature	new	Migrations	dev	Normal			carsten.fuchs@…	Accepted	1	0	0	1	0	0