{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 叼着烟拽天下 的问题《Bugzilla or Mantis? [closed]》','https://www.manongdao.com/q-1305847.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
As the title says, I'm starting one project right now, and trying to layout the infrastructure for the project (SVN, Email, Bug tracking, Online Forums, etc...)
So, Bugzilla or Mantis?
相关问题
- team foundation server bug tracking tools
- Bugzilla: closed-fixed bugs: how to stop further c
- Basic permission in Bugzilla to separate clients
- Best open source bug tracker with Mylyn support
- Is there a simple Bugzilla/Trac client for use by
相关文章
- Is there a simple Bugzilla/Trac client for use by
- Python OO program structure planning
- Bugzilla SMTP authentication
- What tools provide burndown charts to Bugzilla or
- Is there a java api to access bugzilla? [closed]
- Best way to link Redmine issue to SVN revision
- Bugzilla or Mantis? [closed]
- How to reliably reproduce curl_multi timeout while
Mantis is great and simple, simplicity is important as my clients are non technical people.
Another vote for Trac -- dead simple to get going, nice web-based view into your repository, etc.
I think you'll find that your team will like either Trac or Redmine more than Bugzilla or Mantis. Both integrate nicely with Subversion. Both include wiki, forums, project management features...
Quick overview:
Trac: Very widely used and loved, written in python, huge community, lots of "plugins". A common complaint is that it doesn't support multiple projects out-of-the-box, but you can add a plugin to help with that.
Redmine: Written in RubyOnRails. Like Trac, but more complete out of the box. The authors of Redmine are trying to create a better Trac than Trac.
If you are interested in what others searching for bug trackers have written, comparing trackers to each other, I've put some links together here:
http://ifdefined.com/blog/post/2007/10/Links-to-other-comparisons-of-issue-trackers.aspx
If you on Windows, which I'm guessing you aren't, then also consider BugTracker.NET, an easy-to-use, very configurable bug tracking system in .NET/MS SQL Server. (Disclaimer: I'm the author).
I prefer mantis. It performs nicely and is easily extend able either by the use of plugins or with by coding.
Mantis definitely wins on usability grounds over Bugzilla.
In particular, it is just a lot faster to log bugs on Mantis. Time to log bugs is a blocker for some people - I've heard it used as an excuse for not logging them, fixing them and pretending there was never a bug to fix (symptomatic of deeper team problems).
It wasn't until a client (currently using Basecamp, bleah!) canned the idea of Mantis because it wasn't pretty enough that I realised some people (as noted above) think it is ugly.
Compared to Bugzilla or another system we tried implementing, some weird European thing, Mantis is gorgeous.
I know Mantis scales well - a friend used it for the production of the movie Happy Feet. He customised it by adding one extra field to provide another level of categorisation.
I've used bugzilla for a while, but Redmine get my vote. easy setup, very very intuitive.