On 2007-08-23 12:11:55 +0200, "Florian Schmitz"
wrote:
> I don't like a fullscreen box there. It's supposed to
be rather tiny.
> If you need to write essays when closing a task, post a
usual comment
> before closing instead.
I see your point.
It's common (at least on my neighborhood) that developer
mark bug as
resolved and some privileged user (like team leader) closes
it e.g. when
merged into next release. In that case a developer in fact
adds comment
and changes state to resolved. Then the closure comment is
indeed short.
In flyspray it's impossible (?) to do that in only one step
(you have to
add comment and later edit bug and change status to e.g.
ready and
increase Percent complete to 100%) and because of that I
wanted to put
it in closure operation.
Currently in my company resolving (in Mantis) can be called
by svn
commit trigger. Without all in one operation there could be
a problem
with atomic bug resolving (what if second operation
failed?).
Is it planned to add possibility of calling all of that
(explained
above) in only one command (at least by some RPC)?
Regards
Marcin
_______________________________________________
Flyspray mailing list
Flyspray lists.rocks.cc
http://lists.rocks.cc/listinfo.cgi/flyspray-rocks.cc
|
