Broken handling of concurrent ticket changes
|Reported by:||bonefish||Owned by:||nielx|
|Has a Patch:||no||Platform:||All|
(Our?) Trac has two annoying "features" with respect to concurrent ticket changes:
- Modifications of certain (any?) metadata fields of a ticket without adding a comment are not detected as concurrent change. See e.g. #5404. I had this ticket open in a browser and in at the same time marked #5409 a duplicate, setting "Blocked By" to 5404, which automatically sets "Blocking" of 5404 accordingly (cf. change 2). Somewhat later jahaiku added himself to the Cc field (change 3) and a bit later I set the state of the ticket, which was still open in my browser, to "in-progress" (change 4). This also undid changes 2 and 3 without warning.
- When trying to submit a new comment to ticket for which someone has added a comment in the meantime, Trac shows a warning that the ticket has been modified -- which is just fine -- but there's no easy way to acknowledge that and add the comment anyway. One has to copy the comment text, hard-reload the page, paste the comment, and submit it again.
Change History (3)
Note: See TracTickets for help on using tickets.