On Mon, 17 Mar 2014 14:14:49 +0100, Doug Franklin
<nutdriverle...@comcast.net> wrote:
On 2014-03-17 5:53, j. van den hoff wrote:
it is really a
nuisance to look at a seriously misleading/erroneous/misplaced ticket
comment (the more so, if it happens not to be the very last one) and not
being able to correct it.
I just close the broken ticket and start a new one. I even add a "Bad
Ticket" resolution so those cases can be filtered in or out.
thanks. well, this could be a partial solution (or rather workaround) in
certain cases. but for me, the situation currently is as follows:
perfectly valid ticket with several sensible comments including attached
screenshots of the problem addressed by the ticket. _then_ someone
copy+pasted his own comment into the edit window -- but unintentionally
did this for the _wrong_ ticket (his comment concerned something else).
stupid error, but it can happen. so, I cannot simply close the "broken"
ticket, since I cannot easily recreate its (perfectly valid and important)
history (with the exception of the spurious copy+paste error). I also
would have to somehow "fake" the identity of the original ticket issuer
etc.
so the only good solution in my view really would be to restore (if it is
correct that it used to be there...) capability of editing the complete
ticket history. if this history turns out to remain immutable, it would
make life somewhat more complicated. personally, I think it is great, that
checkin comments _can_ be edited after the fact (contrary to some other
DVCSes) -- which addresses excactly the same problem in my view that I
currently encounter with the ticketing system: misleading errors can creep
in which one should be able to correct "in place" and not via "append
only".
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
