id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
8139	order of relations in case of delete or undelete(revert) is unsorted and cause conflict	SunCobalt	team	"JOSM does not recognise the order of stacked relations during the upload( i.e. when uploading deletes or undeletes of relations that are members of a parent relation [which is again member of a parent-parent relation.....]
Steps to reproduce (the easy way)
1. create a node and a way on the relation
2. put both into a relation with only tags type=a
3. create a new relation and put the relation from step 2 in it. add tag type=b to the relation
4. upload...works fine
5. delete....you get an error
Whilst I understand that relations with tags like type=a and type=b should not exist, it shows that in case of super-relations the upload order is random, based on the internal sorting of JOSM. If you turn around ""a"" and ""b"" in the above example, all works fine. Super-relations are more and more common (like for E-Roads)
"	defect	closed	major		Core	tested	duplicate	upload conflict relation