Message-ID: <69153149.13304.1711645996580.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_13303_4723858.1711645996580" ------=_Part_13303_4723858.1711645996580 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Mozilla's Bugzil= la and Atlassian JIRA are among the most popular issue trackers. W= hile they share features common to issue trackers, the systems are very dif= ferent.
=20This article highlights some differences that may be crucial if you are = migrating from one system to another. It is not a comprehensive comparison.=
=20
| =20
Bugzilla | =20
JIRA | =20
---|---|---|
License | =20
Open-Source (MPL) | =20
Commercial (Source code available to commerc= ial license owners) | =20
Server-Side Architecture | =20
Perl | =20
Java (J2EE) | =20
Server Load | =20
Low =E2=80=93 Perl scripts act as simple CGI= s and can be highly sped up with mod_perl. On large databases (>100,000 = bugs) the database may become the bottleneck when doing search queries. You= can also keep multiple Bugzilla instances running on one server without mu= ch overhead. | =20
Considerable =E2=80=93 JIRA is a more comple= x system and typically executes a whole lot more of the server-side code pe= r web request, so the server load is considerably higher (but search in= JIRA may be faster than in Bugzilla due to the Lucene index). Althoug= h you'd need more powerful hardware for JIRA, it will likely do well on a r= easonably modern CPU and 1GB of memory. As a general rule, Atlassian recomm= ends not to store more than 200,000 issues on a single JIRA instance. <= /p> | =20
Access Control | =20
Security groups: quite flexible, but a bit m= ind-bending feature for grouping users & issues and granting permission= s. | =20
JIRA has more simple permissions model, more= conventional and arguably more convenient. Migrating from Bugzilla securit= y groups might be not an easy task. | =20
Flags/Requests | =20
This is a quite unique Bugzilla feature. | =20
Labels in JIRA can be used as basic flags (w= ithout the assignment of a "?" flag). Excellent extensibility leaves room f= or a plugin that mimics Bugzilla's flags feature more precisely. | =
=20
Search Power | =20
Bugzilla's advanced search is quite powerful= , especially when it comes to all the options available in the Boolean Char= ts and high-precision searches like regexp matching. Mastering all the opti= ons and understanding how Boolean charts work could be a challenge though. = | =20
JIRA has flexible JQL language (JIRA Query L= anguage) that allows you to build arbitrary boolean expressions. The interf= ace for writing a query is a text box with auto-completion and error highli= ghting, and is generally more usable than the large Bugzilla's form. JIRA l= acks some of the expert-level search conditions that Bugzilla can do and se= arching for text in JIRA issues may be limited by how Lucene index works. T= hird-party plugins can extend JQL functionality through custom functions. <= /p> | =20
Security | =20
Due to full open-source code exposure and us= age by Mozilla and some other big players, Bugzilla's security should theor= etically be very high. Bugzilla team publishes security advisories and rele= ases security patches in a very reasonable time. | =20
Atlassian takes security seriously and publi= shes security advisories and patches when security threats become known. Co= mpared to Bugzilla, JIRA security risks are somewhat higher due to the larg= er overall complexity, a lot of client-side JavaScript code, and additional= functionality provided by 3rd-party plugins. | =20
User Interface | =20
Bugzilla user interface hasn't changed much = over the years. Some usability improvements have been added, but overall, n= othing fancy. The HTML is generated from templates, and some companies have= modified those templates to make Bugzilla look a lot better. | =20
JIRA user interface by far better than Bugzi= lla, out of the box. A lot of effort has been put into it, and it's being c= ontinuously improved. | =20
Custom Field Types | =20
Types available in Bugzilla: | =20
Custom field types available in JIRA are too= many to list, and even more custom field types available from plugins. | =20
Custom Field Values / Conditions | =
=20
Bugzilla lets you show/hide the whole custom= field or specific values based on the value of some other field. | =
=20
JIRA allows conditional configuration based = only on Project and Type fields. | =20
Workflow | =20
Bugzilla lets the admin define a global work= flow for all Products by editing transition matrix (each cell allowing tran= sition from status A to status B). Unlike JIRA, Bugzilla can let users sele= ct the initial status of a new issue and lets the admin configure which tra= nsitions require comments. | =20
Unlike Bugzilla, JIRA allows to define multi= ple workflows which are applied based on the issue's Project and Type. Each= workflow may transition issue through a subset of statuses, with each tran= sition possibly having a separate set of fields (Screen) that the user can = fill out when doing the transition. Transitions may have pluggable, configu= rable conditions and post-functions. Overall, JIRA workflows are far more p= owerful albeit missing some features available in Bugzilla. | =20
Issue Linking | =20
Bugzilla has only one link type: blocks/depe= nds, plus a Bug ID custom field. | =20
JIRA has configurable link types with user-d= efined semantics. JIRA also has pluggable remote issue links, that allow to= link an issue to any other entity outside JIRA. | =20
Plugins, Addons, Customizations | =20
Bugzilla has a few Bugzilla Add-Ons. U= nofficial Bugzilla patches may be found on the Internet. | =20
JIRA functionality can be extended and alter= ed by plug-ins to a very large extent. Atlassian has a thriving developer e= cosystem with their own Plugin SDK, and JIRA has rich set of APIs that make= it easy to create powerful plugins. Lots of JIRA plugins are listed on Plugin Excha= nge. | =20