Modify ↓
#5785 closed defect (duplicate)
Fails to recognise closed changeset
| Reported by: | Cobra | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | Cc: |
Description
The upload dialog acts a little stupid when…
- it is set to upload to an existing changeset (with ID 42 and comment "xyz")
- this changeset (42) is closed by the server
- the list of open changesets is updated
After the last step JOSM knows that the selected changeset 42 is closed already but doesn't change the settings to "upload to a new changeset". It will still try to upload to this closed changeset which will (obviously) fail.
It would be nice to check whether the selected changeset is still open every time the list of open changesets is updated and change the upload settings according to the results.
Attachments (0)
Change History (4)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Summary: | Automatically update upload settings after manually updating the list of open changesets → Fails to recognise closed changeset |
|---|---|
| Type: | enhancement → defect |
Changing to defect in light of the above.
comment:3 by , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
This seems to be the same thing described in #4370.
Note:
See TracTickets
for help on using tickets.
Confirmed for r3966. The list of open changesets includes closed changesets. When you attempt to close them, you get an exception, and a message that the changeset is already closed, yet it is not removed from the list of open changesets.