Step wrote, at 09/18/2008 01:21 PM:
> Original description and Internal note are important parts of the
> issue. Once entered, those can never be removed nor edited. I belive
> that this is extremely important. To be honest, I do not like the
> idea of Delete Internal Note too. :)
I like the flexibility, myself. I don't do it often, but I've had to
alter the original summary/description of an issue, usually when the
initial report was vague or the problem was discovered to be elsewhere.
> How else can you be sure you have the complete picture of what is
> happening? Especially if you are the one who starts to work on a
> Issue at the later time.
It might be nice to see a changelog of such updates, but I can refer to
the original email that started the issue, in most cases.
> In short: Update issue (ticket) = add Internal note and change all
> the other parameters (like status, assigned to etc) if necessary.
You can make that a matter of policy (or patch the source), but I agree
it would be nice to have a configuration option or access control to
mark these as uneditable.
