id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
4215	Changeset object counter	Ldp	team	"Assuming that changesets are usually opened, processed, and closed from within only 1 running JOSM version at the same time, it would make sense to add a counter to tell how many objects were already uploaded, and how many can still fit until hitting the limit.

Uploading more objects than the changeset can hold could result in a user warning before the upload starts, or when in chunked mode, could offer to open a new changeset with the same tags, once the changeset limit is approached or hit.

I understand that fetching the changeset object counter when scanning for open changesets may be harder, but if that is still doable without causing too much API load, that would also be excellent.

A user juggling the same changeset between multiple JOSM versions is already in Here Be Dragons-mode, so the counter being wrong there won't matter that much."	enhancement	new	normal		Core