Opened 16 years ago
Last modified 7 years ago
#4535 closed enhancement
Silly "changeset already closed" — at Version 4
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | 18.10 |
| Component: | Core | Version: | latest |
| Keywords: | upload changeset | Cc: | planemad, zuse |
Description (last modified by )
- Edit some data with josm, have an open changeset
- Press upload
- JOSM closes the upload dialog, displays a "changeset already closed" error
- Try to upload again, not changing any settings
- JOSM opens a new changeset and uploads
Why can't it go from 3 -> 5 automatically without bothering me?
Change History (4)
comment:1 by , 16 years ago
| Type: | defect → enhancement |
|---|
comment:2 by , 16 years ago
Often I have the case where it keeps looping back to 3 if I try 4. Not always.
I notice a few more tickets and even a non-filed issue I have, about changeset handling, especially related to autoclosed changesets, and I think they are likely all related. Whenever JOSM encounters autoclosed changesets where it itself thought it was still open, it doesn't always pick that up correctly. Sometimes it takes a few tries with the changeset tab in the upload dialog, or just a few retries on upload, before it picks up the actual changeset status from the OSM server.
comment:4 by , 13 years ago
| Cc: | added |
|---|---|
| Description: | modified (diff) |
Note:
See TracTickets
for help on using tickets.
Good point. Of course it can, unfortunatelly it doesn't ;-)
"Defect" is too harsh, isn't it? Reclassifying as enhancement.