On Thu, Dec 8, 2011 at 8:14 PM, Tully Foote wrote: > I definitely agree that this is becoming a challenge to manage and we should > make sure it is easy to use. > I think that we should identify the primary use cases and make sure that > they're well documented, and make it part of the release review process. > > The three use cases I see as the biggest are as follows with the easiest > fixes: > > Where do I file a ticket? > Solution: Fix links on stack pages.  (Improve them for external tracker > support; external repos often need to hard code the links.) Most users have trouble figuring out what component is failing. Even developers have trouble sometimes. > What tickets are open against this component? > Solution 1: Fix links on stack pages (Improve them for external tracker > support; external repos often need to hard code the links.) > > What tickets are assigned to me? > Solution: For the next release of kforge there is going to be a personal > aggregator for all your tickets.  It would seem that this infrastructure > could be extended to aggregate over customizable external repos.  Just give > kforge the url, tracker type, and your username to query the databases. These are mostly developer questions. We generally know where our components are tracked already. --  joq