Opened 10 years ago
Closed 10 years ago
#11527 closed defect (worksforme)
Upload to new changeset reuses open changeset
Reported by: | BearT | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
I'm using JOSM latest, currently 8465. Since some time now I've got problems when choosing to upload to a new changeset, when the previously uploaded changeset (in the same JOSM session) is not closed. Instead of actually opening a new changeset the open changeset is reused which leads to wrong changeset comments and possibly spatially huge changesets that do not have anything in common, except they were done in the same JOSM session.
If this is intended behaviour this should also reflect in the GUI, ie. in the upload dialog not mentioning the "new changeset".
Attachments (0)
Change History (3)
comment:1 by , 10 years ago
comment:3 by , 10 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Thanks for the duplication hints. I've searched Trac before posting, but obviously I didn't find these two.
I just tried to reproduce this behavior to compare to your examples and found this is fixed in r8471. Thanks for that.
What JOSM currently does is creating an initial open changeset. When I try to upload the second changeset the GUI tells me something like "This will be uploaded to an existing open changeset with 'Changeset comment'". If I choose "Changeset > Upload to new changeset" a new changeset is created as expected.
PS: I've closed this as worksforme only, since I do not know where the fix has been applied. Feel free to change it and link that ticket to the commit.
PPS: If I understand correctly this seems like a duplicate of #10946 but I'm pretty confident I did not see that problem for 5 months now (when #10946 has been reported). So it may have been fixed already and accidentally recreated or there may be multiple causes for a similar behavior.
This bug is not directly related to #4003 though the fixed behavior I described above seems to also fix #4003. This new, detailed upload view has been proposed in comment 4 of #4003 .
Looks like a duplicate of #10946