>>that list is HUGE! You definitely don't want such a big list in a simple
>>floating dropdown box. You need a separate window with scrollbars and
>>enough space to show at least a small part of all those issues to not
>>loose the oversight.
Actually I wouldn't want such a huge list _at all_. If it is as big as
that is probably depends on habits inside an organisation. Even in a
large project spanning a few years and involving ~10 developers we
_never_ had as many issues open at a single point in time. It's a matter
of frequently evaluating the validity of opened bugs.
In some cases simply returning all open/active issues might not be
enough. Maybe we would need to give that some more thought.
One suggestion that comes to mind would be to optionally submit the user
name as part of the URL of the request to the issue tracker (add
something like %USER% to bugtraq:ticketrequesturl or similar). That way
it could return e.g. only the tickets assigned to that user.
Some client-side configurable filtering of the results of the request
might be another idea (let the user specify which tickets he wants to
see generally, e.g. only those which belong to a specific component).
This could be done in some generic way, e.g. with a delimiter-separated
list: "column3 = mycomp" meaning show only the results which have
'mycomp' as value in the third column. The above assigned-user filtering
could be done that way too.
Lars.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 21:47:50 2004