id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
12873	Should close the changeset when splitting it at the 50k limit	naoliv	team	"Already saw this happening 2 times with friends: while uploading a very large changeset, with more than 50000 objects, JOSM splits the changeset (as it should, due to the [https://wiki.openstreetmap.org/wiki/API_v0.6#Response 50000 maximum elements limit]).
But there is one issue: JOSM closes only the last changeset, leaving the first ones to be closed automatically by the API timeout.

For example, one changeset started here https://www.openstreetmap.org/api/0.6/changeset/39411216 at 21:16 hours then JOSM started a new one here https://www.openstreetmap.org/api/0.6/changeset/39412061 at 22:00.
Note that the second changeset was then closed at 22:27 while the first one was closed at 23:00 (since it hit the 1 hour API timeout).

Before creating a new changeset in cases where a split is necessary, JOSM should first close the older one and only then continue the needed actions."	enhancement	closed	normal		Core		duplicate