#3992 closed defect (worksforme)
Ticket last modified date is incorrect
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.10 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
If you look at ticket:230, you'll see that the last change listed was ticket:230, comment:12 on 04/10/2006 10:28:56 AM
, but the Last modified date listed at the top of the ticket says 2 weeks ago.
It should be 6 months ago… unless you can make changes to the ticket without updating the change history.
Attachments (1)
Change History (7)
by , 18 years ago
Attachment: | last-modified-screenshot.png added |
---|
comment:1 by , 18 years ago
Added a screenshot in case the ticket changes before you have a chance to debug this (so you believe me ;) )
comment:2 by , 18 years ago
Summary: | Ticket last modified date appears incorrect on ticket:230 → Ticket last modified date is incorrect |
---|
Same thing with ticket:1514, except it was last updated over a year ago, but Last Modified says "2 weeks ago".
follow-up: 5 comment:3 by , 18 years ago
That must be due to the TicketDeletePlugin, which doesn't reset the modified date. I'm note sure if this is a defect or a feature (at least now there's a way to detect that changes were deleted…)
comment:4 by , 18 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Alright, I'm okay with that answer. I just wanted to point it out in case it was a bug.
comment:5 by , 18 years ago
Replying to cboos:
That must be due to the TicketDeletePlugin, which doesn't reset the modified date. I'm note sure if this is a defect or a feature (at least now there's a way to detect that changes were deleted…)
I still haven't heard a reason to force one behavior or the other. It should probably be configurable through trac.ini.
comment:6 by , 18 years ago
I think this is something that should be addressed in the th:wiki:TicketDeletePlugin. IMHO, it is somewhat weird to have a modified date with no information related to the modification. To quote cboos, it's more a 'bug' than a feature to me, as long as the user has no way to understand how the last modification date has been set.
screenshot of the wrong last modified date