[patch] unique timestamps needed for use with MasterTicketsPlugin
|Reported by:||abbywinterscom||Owned by:||farialima|
When TicketImportPlugin is used with MasterTicketsPlugin there can be a problem is 2 tickets are imported/updated that both are "blocking" the same ticket. This is because the MasterTicketsPlugin will, as a side effect, update the "blockedby" field of the parent ticket. This means that 2 rows in the same import spreadsheet may cause 2 side-effect updates to a single ticket. This means that (ticket,time,field) will not be unique for these 2 changes in the ticket_change table.
In order to rectify this, we should use a different time stamp (increment by 1 second) as when_ts for each row in the spreadsheet. This is the "standard" work around for bulk updates in Trac, because it is the only way to make each row emulate a separate change submission.
I've attached a simple patch to address this issue.
Change History (5)
Changed 7 years ago by abbywinterscom
comment:1 Changed 6 years ago by hasienda
- Summary changed from timestamp uniqueness in combination with MasterTicketsPlugin to [patch] unique timestamps needed for use with MasterTicketsPlugin