id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
20425	[Patch] Duplicate Relation test is too lazy/too aggressive	GerdP	team	"Follow up of #20393, #20424 and #19956
The test that produces message ""Duplicated relations"" is a quite misleading. With the current implementation (r17476)
- it ignores all tag keys returned by `AbstractPrimitive.getUninterestingKeys()` (e.g. {{{description, note, fixme, comment}}})
- it ignores members which appear multiple times (eg. two times in one relation, only once in the other)
- it ignores the order of members (wich is good for multipolygons but not for route relations)
It's too lazy because 
- it will flag two multipolygon relations with the same tags and the same geometry if they use different ways, but only when those different ways have the same nodes in the same order and the same tags, so I am not sure if the test really tries to find the equal geometries.
- it ignores relations with identical member lists when any of the members isn't downloaded (#20242)

The major problem: It offers an autofix which also ignores these differences and might remove the ""better"" version of a relation, e.g. it might keep the one with the fixme tag.
I wonder if I should try to improve the code or better simply remove the autofix or the complete code.
"	defect	closed	normal	24.02	Core validator		fixed