> We have recently installed version 1.8.5 with its new "Obsolete" state
> and found that it would be very useful if the "Create new topic" form
> that is used when obsoleting an old topic would populate its fields with
> the values used by the obsolete topic. This would make it very easy to
> create a followup topic based on the review comments of the first topic
> without having to re-enter all the fields. If this functionality is
> added it would make sense to have a "Clear" button and possibly a "Copy
> from obsolete topic" button on the form.
That makes sense. I'll add that to the list.
> An unrelated feature request that we would find very useful is the
> ability to add a comment that is not associated with any particular line
> number. Similar to this it would be useful for reviewers to be able to
> set a flag or something that states that they are finished looking at it
> - sort of a "No more comments" button. We generally do this now by
> adding a comment to that effect on the last line of the review or by
> simply assuming that silence means acceptance, it would be handy if
> codestriker explicitly supported some sort of acceptance or no more
> comments function.
Release 1.8.6 has the ability to add general comments applying to a file,
or indeed to the entire review, so you could use the entire review link as
a way of achieving this. Hopefully this release will be out in the next
couple of weeks.
Your last part is about adding in a state for each reviewer. At the
moment, like you, most people are doing this informally by adding comments
at the end of the review.
Adding a state in would allow us to do actions as a consequence of events,
such as when all reviewers "accept" a review, for example. Or flag those
people who haven't done their reviews - kind of like a 'nag' feature. :)
Its not high on my list of necessities, but if somebody wants to implement
it, more than happy to accept it as an optional feature.