Question about journal table / roundup- admin history vs. item webpage history section

Good day, Roundup Users. I am confused about the difference between the journal and the history. I'm try to report on how long a given issue was open (from creation though setting to a resolved status).

I'm sure there are better ways than what I'm trying (and of course I'd love to hear the ideas). But in the meantime, I'm finding the data in the journal table and history in roundup-admin confusing when compared to the history as shown in the issue web page.

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.

I'll add the history from roundup-admim and the history from the item page. I added some newlines in the history to make it easier to read.

roundup-admin history for issue88963
==================================
roundup> history issue88963
[
('88963', <Date 2019-12-01.22:55:47.596>, '619', 'create', {}),
('88963', <Date 2019-12-01.22:58:23.287>, '619', 'set', {'status': '1', 'messages': (('+', ['743004']),)}), 
('88963', <Date 2019-12-02.11:58:35.979>, '207', 'set', {'status': '3', 'assignedto': (('+', ['186', '207']),), 'messages': (('+', ['743033']),), 'nosy': (('+', ['186', '207']),)}), 
('88963', <Date 2019-12-02.12:06:32.307>, '207', 'set', {'messages': (('+', ['743036']),)}), 
('88963', <Date 2019-12-02.13:44:27.199>, '81', 'set', {'messages': (('+', ['743165']),)}),
('88963', <Date 2019-12-03.11:53:29.162>, '207', 'set', {'status': '8', 'messages': (('+', ['743566']),)}), 
('88963', <Date 2019-12-03.12:11:02.207>, '207', 'set', {'status': '4', 'messages': (('+', ['743572']),), 'causes': None}),
('88963', <Date 2019-12-16.13:09:59.012>, '207', 'set', {'status': '8', 'messages': (('+', ['747146']),)})
]

issue.item.html page for issue88963
================================
History
Date	User	Action	Args
2019-12-16 13:09:59	esantiag	set	status: waiting for customer feedback -> closed (customer contacted)
messages: + msg747146
2019-12-03 12:11:02	esantiag	set	status: in-progress -> waiting for customer feedback
messages: + msg743572
causes: FANS/ATN
2019-12-03 11:53:29	esantiag	set	status: waiting for customer feedback -> in-progress
messages: + msg743566
2019-12-02 13:44:27	adc	set	messages: + msg743165
2019-12-02 12:06:32	esantiag	set	messages: + msg743036
2019-12-02 11:58:35	esantiag	set	status: chatting -> waiting for customer feedback
assignedto: + impltech, esantiag
messages: + msg743033
nosy: + impltech, esantiag
2019-12-01 22:58:23	rmatos	set	status: unread -> chatting
messages: + msg743004
2019-12-01 22:55:47	rmatos	create	

So it's as if the 'set' 'status' in the history and the journal table are showing the status BEFORE that entry was submitted. If this is expected, please let me know and I'll figure out how to handle it.

And again, if there's a better/easier way to extract time between creation and resolution, please point me in the right direction.

Roundup is fantastic, of course; we're been using it with very little customization since 2003.


-- 
  David Hancock
  [email protected]