We currently use bugzilla and would like to consolidate systems as much as possible.
I was wondering if anyone had migrated from Bugzilla over to Sugar's tracker and if so what their experiences were. Would they do it over again? Any major limitations of Sugar's Bug Tracker?
One I can think of is Bugzilla out of the box works with lots of other tools like Eclipse Mylyn... but I figure if we're using the CRM daily anyway for support and order tracking (developers wears multiple hats in our company)... it's not as important to be able to access Bug Tracker form within development environments.
Can anyone share their experiences with using the Bug Tracker in a more recent version of Sugar. I searched the forums and found some posts from approx 2007 and one poster had the following complaints with sugar. Don't know if any have been resolved upon by now:
Off hand it looks like #3 and #7 are the only ones I really care about... I assume #5 can be accomplished with the reporting capabilities in the pro/enterprise versions of sugar.1) No parent child relationships between defects within the Sugar bug tracker
2) Notifications are only sent to the assigned resource and not the manager
3) No way to assign defaults by product
4) No way to remove the mass update feature by role
5) No reports with graphs for BugTracker
6) Can't make existing fields required
7) No way to limit other drop downs based on other selections i.e. Product X Version A,B,C if you select Product Y Version 1,2,3
Source: http://www.sugarcrm.com/forums/showt...light=bugzilla


LinkBack URL
About LinkBacks



Reply With Quote

Bookmarks