Re: Question about journal table / roundup-admin history vs. item webpage history section
Ralf Schlatterbeck <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
On Sun, May 24, 2020 at 11:12:45PM -0400, David Hancock wrote:
> Here's an example. issue88963 is resolved (we call its status "Closed
> (customer contacted" and the status id is 6). I would expect the last
> entry for it in the journal table to show setting status to 6, but
> instead, the 'set' shows the status prior to closing ("Waiting for
> customer feedback, index 8). The timestamp of the last 'set' is the
> timestamp when the issue.item page shows it was set to Closed.
The journal always lists the value *before* the logged change. The
history display re-computes the changes by going backwards through the
journal. The latest value is only in the database.
You may want to study the code in roundup/cgi/templating.py
the function is named (you guessed it) "history" and belongs to the
_HTMLItem mixin.
Ralf
--
Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16
Open Source Consulting www: http://www.runtux.com
Reichergasse 131, A-3411 Weidling email: [email protected]