From: David A. D. <de...@gn...> - 2005-01-07 18:02:13
|
> We are hoping to use mantis for a customer issue tracker (not so > much a bug tracker) in our small-medium sized company. I imagine > "projects" will be our "departments". That's one approach. Another is to use "Projects" to assign "groups" within your departments, and use the Category system within Mantis to assign to departments or projects themselves. > The only major thing I see missing, is a way to seaerch for > resolutions to similar problems before a new issue is logged. That should be fairly simple to add. You could simply "delay" the posting of the new incident to the database, and use the Summary and Description fields to run a quick search across existing reports, and provide the user with a list that might match: "Similar reports to yours were found. Would you like to add a Note to those existing reports, or continue to report your incident as a New issue?" > But I really like its design and ease-of-use. Views, filters, > reports, and other info is very well laid-out. We tested something like 14 bugtrackers and incident trackers years ago before we finally settled on Mantis. We've stuck with it ever since. Its easy to use, easy to modify, and runs against the same philosophy that we believe in. David A. Desrosiers de...@gn... http://gnu-designs.com |