Here’s a copy of an answer I have sent to someone who asked me to compare JIRA and Bugzilla:
如果别人问我jira和bugzilla有啥区别，我就支持copy这篇东东给他。
Things that Bugzilla does and JIRA does not:
bugzilla能做到的/jira不能做到的：
1. Bugzilla is very good at performance with large bug databases. Take a look at bugzilla.mozilla.org, it has ~400,000 records. I’m not sure what hardware it runs on, but you will probably need a lot more for the same stuff on JIRA. It’s just Perl vs. J2EE. But if you have fewer than 50,000 records, don’t worry.
bugzilla在数据量庞大的时候有很好的表现，看看bugzilla.mozilla.org就有超过40w数据（-_-||，这就算庞大了？），我不知道它的硬件配置是什么，不过如果你要jira也处理这么多数据，硬件要求肯定比较高。其实这就是perl 和 j2ee的性能对比。不过如果你只有小于5万条数据，上面说的都不用担心。
2. Flags/requests. If you use this Bugzilla feature, you won’t find anything similar in JIRA. But probably there’s a plug-in.
标志/请求（没仔细用过，不清楚），如果你要用这个功能，jira暂时貌似还不提供，不过可能有插件提供了，自己找找。。。
3. Authorization is different. Bugzilla has a mind-breaking feature for grouping users & issues; JIRA has something more simple (and more convenient, I think). But if you have defined a lot of security groups in Bugzilla, it may be not easy to transfer their business logic to JIRA.
用户验证和权限控制是不同的，bugzilla有创新的用户和事件分组特性；jira只有简单的方式（不过更便捷）。如果你已经在buzilla里面定义了很多安全分组，要把这些逻辑转移到jira不是那么容易实现。
4. Search in JIRA is far less powerful than Bugzilla’s advanced search.
bugzilla的高级搜索比jira强大。
5. If your Bugzilla is patched or integrated with other systems, take a close look at that.
如果你的bugzilla打过补丁、和其它系统耦合在一起，想转移到jira就要好好研究一下了。。。
6. Bugzilla is free and open-source, if that does matter.
buzilla是免费开源的，不过如果你不在意，就略过这点。
7. Bugzilla’s security theoretically should be better, because of (6).
bugzilla的社区支持理上比jira好，原因如6。
But there are also reasons to move to JIRA:
也有不少理由支持我们转移到jira
1. Web-based user interface is better.
用户界面更加优秀（优秀很多。。。）
2. JIRA supports custom fields of many types. (Someone: This is available in Bugzilla 3.0; IgorSereda: As far as I know, only text and select fields are available.)
jira支持自定义字段和类型（有人说：bugzilla 3.0 也开始支持了，没用过，不清楚，貌似只支持文本的和选择框）
3. JIRA (enterprise edition) supports a number of customizable workflow schemes (Bugzilla has only one non-customizable hard-coded workflow). (Someone: Customizable workflows are planned for Bugzilla 3.2)
jira支持自定义工作流（bugzilla只有一个固定的工作流）。（有人说：bugzilla 3.2也将要支持这个功能啦。。。汗。。。还是有竞争好。。。）
4. JIRA issues may be linked with custom link types of user-defined semantics.
jira的事件可以通过用户自定义的方式来访问。
5. JIRA has open architecture and a plug-in API and lots of plug-ins. If JIRA doesn’t do something, you might find a plug-in for that.
jira有开放的插件api体系和一大堆插件。如果jira不能支持某个功能，你或者可以找到一个插件可以支持的。
6. JIRA has very good commercial support. (Someone: The commercial Bugzilla support is excellent, too)
jira的商业支持很好（有人说：bugzilla的商业支持一样很优秀）
Leave a Reply