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
23410	Backward migrations change overall state rather than reverting single migration	Markus Holtermann	nobody	"When rolling back to a previous migration (or more precisely: state), Django reverts all migrations between the current state and the one that point in history looking at the linear migration plan. Taking the example from the tests (https://github.com/django/django/blob/1a918806ca67e8e4818aeb1c304e4546baab9e4d/tests/migrations/test_graph.py#L47-L50) and the behavior how South handled backwards migrations, this is somehow inconsistent and might even lead to data loss. I'd expect nothing to happen in the example above.

Looking at the more complex example from the tests (https://github.com/django/django/blob/1a918806ca67e8e4818aeb1c304e4546baab9e4d/tests/migrations/test_graph.py#L101-L104) I wouldn't expect `c.0001` being rolled back, instead `a.0001`, `a.0002`, `b.0001` and `c.0001` should still be applied."	New feature	closed	Migrations	1.7	Normal	fixed		Markus Holtermann github@… Shai Berger	Ready for checkin	1	0	0	0	0	0