Opened 13 years ago
Closed 13 years ago
#10338 closed defect (fixed)
Deleting first ticket change does not reset changetime correctly
Reported by: | osimons | Owned by: | osimons |
---|---|---|---|
Priority: | normal | Milestone: | 0.12.3 |
Component: | ticket system | Version: | 0.12dev |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
The change in #3641 / [9270] works fine as long as earlier ticket changes exist. However, if no such ticket change then exist, the changetime
will be set to NULL
.
If so, the # Fix the last modification time
part of Ticket.delete_change()
needs to use time
from ticket
instead of ticket_change
so that last modified will be set to time of ticket creation.
Attachments (0)
Change History (5)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Good catch Simon. We could maybe get away with simply adding UNION SELECT time FROM ticket WHERE id=%s
to the sub-query (and passing the additional self.id
argument), or possibly use COALESCE()
.
Do you want to fix that yourself, or should I look into it?
comment:5 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Meaning "first and only" ticket change of course - which also makes it the "last" change I suppose :-)
Anyway…: