id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
17866	Merging nodes: youngest instead of oldest id and history kept	skyper	team	"==== What steps will reproduce the problem?
1. Have an node and another node with higher id than the first one.(568979540, 3825090301)
1. select them (order does not matter)
1. merge them with menu function or keyboard shortcut 'm'

==== What is the expected result?
Lowest Id and history of the oldest node is used/preserved.
==== What happens instead?
Id and history of the younger node is used.

==== Please provide any additional information below. Attach a screenshot if possible.
Thought the order of selection did matter some time ago.
Strange, it seems to happen only on some sessions.

{{{
URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-06-24 20:49:39 +0200 (Mon, 24 Jun 2019)
Build-Date:2019-06-25 01:30:58
Revision:15195
Relative:URL: ^/trunk

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.
}}}
"	defect	reopened	normal		Core	latest		template_report merge node history