Roundup Tracker - Issues


Author rouilj
Recipients antmail, ber, jerrykan, rouilj
Date 2016-06-26.19:11:56
Message-id <>
I am confused.

Is this the same problem as: 

 issue1169513: History breaks when props are inaccessible

or something more? (Added the link to superseder to make
sure this possibly related issue isn't lost in the message history
although it's not really a superseder).

Using jerrykan's reproduction steps in msg4512
in the current classic tracker only produces:

Required issue property title not supplied 

as an error and the history looks like:

2016-06-26 19:04:20	admin	set	assignedto: admin ->
2016-06-26 19:03:54	admin	set	assignedto: admin
2016-06-26 19:03:49	admin	create

was this fixed and this ticket not closed?

Do I need to have a date field in the schema to see this issue?

If the problem is that an entry is added to the history
even though the entry was rolled back by an auditor error
that seems to be a different diagnosis.

This tracker is using sqlite back end. If the problem is a history
non-rollback maybe this only affects anydbm backends?

I would like to get rid of known crash bugs with patches in the 
next (1.6) release if possible.

-- rouilj
Date User Action Args
2016-06-26 19:11:57rouiljsetmessageid: <>
2016-06-26 19:11:57rouiljsetrecipients: + rouilj, ber, jerrykan, antmail
2016-06-26 19:11:57rouiljlinkissue2550612 messages
2016-06-26 19:11:56rouiljcreate