Sounds about right. The day is incrementing correctly. It now says 18 days. It’s not just my tickets, it’s all of them. Eg, take a look at the Project tag report
It’s likely that I ran a batch on the tickets which touched their updated_on fields outside of the application. We’ll have to wait and see if your new tickets still display incorrect information.
Can you let me know the ticket numbers brook? I’ve just realised these may pre-date the code that generates events for changed titles and descriptions.
Dan Glegg (Project owner)
Yep, I’m pretty convinced that this was a development snafu. No biggie.
Brook Elgie (Project member)
Sounds about right. The day is incrementing correctly. It now says 18 days. It’s not just my tickets, it’s all of them. Eg, take a look at the Project tag report
Dan Glegg (Project owner)
It’s likely that I ran a batch on the tickets which touched their updated_on fields outside of the application. We’ll have to wait and see if your new tickets still display incorrect information.
Brook Elgie (Project member)
I have no tickets that say they are older than 17 days.
59, 73, 70, 71, 69, 60, 61, 62, 66, 65, 64, 63, 72, 68 – all have 17 days, but are actually older than that.
Dan Glegg (Project owner)
Can you let me know the ticket numbers brook? I’ve just realised these may pre-date the code that generates events for changed titles and descriptions.
Dan Glegg (Project owner)
Odd – it’s possible that something has altered that ticket that didn’t record an event – I can’t think what that would be though. I’ll have a ponder.