﻿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
26906	Factor out an AlterFooTogether operation from AlterUnique/IndexTogether	Akshesh Doshi	Akshesh Doshi	"The reasons why I think this should be done are

1)  When a bug is reported for any one of them (like #26180) the owner or reviewer has to check if the bug also exists (most of the time it does) for the other operation and apply the same fix for the other (see [https://github.com/django/django/pull/6926/ !6926]), or else the fix might get delayed until another ticket is opened reporting the same issue for the other operation.

2) Recently I realized that a small part of `AlterIndexTogether` code is untested but tests exist for those lines for `AlterUniqueTogether` so having the same source of code for both the operations will result in better code coverage!

3) More than 90% of the code for both the operations is the same so in honor of the DRY rule (this is maybe kinda the reason for point 1 :P).
"	Cleanup/optimization	closed	Migrations	dev	Normal	fixed			Someday/Maybe	0	0	0	0	0	0
