id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
8251	User names that have changed	aliponte	team	"JOSM gets confused, if a user changes his name. Suppose you stored an osm file containing a certain node which was last edited by user ""ABC"". Some time later you load this file again, but in the meantime this user changed his name to ""DEF"". If you activate the version protocoll of the node mentioned above, then you'll find user=DEF/ABC. JOSM seems to concatenate the old and new name. Crucial is, what JOSM does when you store this osm file again. You'll find the code user='DEF/ABC' being stored. If you load this file, activate the version protocoll and save this file repeatedly, the user name being stored in the osm file gets longer and longer. Why does JOSM care about the old user name? Why doesn't it just write user='DEF' into its updated osm file version?

As an example I attached a short osm file which is showing what I tried to describe. "	defect	closed	normal	16.08	Core	tested	fixed		aliponte