Lars Klose <lars.klose@klst.com> wrote on 10/27/2004 02:41:34 PM:
> >>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.
I would presume that in many cases the user would be prompted to login by
the bug tracking system, and then it would only show them their bug's. The
problem with %USER% is what do you substitute? The Windows ID may or may
not be their ID for the bug tracking system. I wouldn't be against having
a %USER%, just pointing out there might be other ways to handle it.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
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:57:50 2004