|
From: Ivo v. D. <ivo...@gm...> - 2008-01-03 09:20:50
|
Well, actually no. To make bug management viable we need some support from our users in making sure bugs aren't reported over and over. One tracker with a clear layout would make it easy for a user to search for a known issue before reporting a new one. If we keep a separated tracker we can't expect users to search both of them (we're lucky if they take the time to report a bug at all :)). On a side note: How do we move issues from one tracker to another? This would be very useful to move some bugs to the features tracker. Ivo On Jan 3, 2008 10:13 AM, Mattijs Hoitink <ma...@fu...> wrote: > I just had a look at the SF tracker system and saw the option to add a > new tracker. The add screen contains the following text: > > "You can use this system to track virtually any kind of data, with each > tracker having separate user, group, category, and permission lists. You > can also easily move items between trackers when needed." > > Would it be a good idea to create a developer tracker where we van put > the core issues for developers. We could create detailed core categories > in that tracker. This would make sense as we don't want to hassle user > with development issues. > Bugs can stay in the separate tracker for bugs where user can report > them with the global categories. > > Sounds good? > > cheers > > > Mattijs Hoitink wrote: > >> How about something like this: > >> > >> Frontend > >> Core > >> Configuration > >> Packaging > >> Plugin system > >> Documentation > >> Other (facilities like maven repo, demo, nightly, etc) > >> > > I can agree with the more general categories, it seems less complex for > > other users. Still, I think it would be wise to have a little more > > categories for the core. If developers want to use the tracker to place > > issue that need to be addressed within the core, and assign issues to > > other developers, it would be nice if they could be a little bit more > > specific in the part the issue is concerned with. > > > > Maybe it's a good idea to have a little more core categories? Like: > > > > Frontend > > Core > > Core - Presentation > > Core - Managers > > Core - DAO > > Core - Datebase > > Configuration > > Packaging > > Plugin system > > Documentation > > Other (facilities like maven repo, demo, nightly, etc) > > > > I don't think the SF tracker supports sub categories (stupid!), so the > > prefix Core should make it clear for non developers what the category is > > about. > > > > cheers > > > > -- > > Mattijs Hoitink > > Func. Internet Integration > > W http://www.func.nl > > T +31 20 4230000 > > F +31 20 4223500 > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Webical-developers mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webical-developers > > > > -- > Mattijs Hoitink > Func. Internet Integration > W http://www.func.nl > T +31 20 4230000 > F +31 20 4223500 > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Webical-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webical-developers > -- Ivo van Dongen Func. Internet Integration W http://www.func.nl T +31 20 4230000 F +31 20 4223500 |