Unlike JIRA, Bugzilla can let users select the initial status of a new issue and lets the admin configure which transitions require comments. JIRA allows conditional configuration based only on Project and Type fields.īugzilla lets the admin define a global workflow for all Products by editing transition matrix (each cell allowing transition from status A to status B). Text fields, Multi-selection, Drop-down, Date/time, Bug IDĬustom field types available in JIRA are too many to list, and even more custom field types available from plugins.īugzilla lets you show/hide the whole custom field or specific values based on the value of some other field. A lot of effort has been put into it, and it's being continuously improved. JIRA user interface by far better than Bugzilla, out of the box. The HTML is generated from templates, and some companies have modified those templates to make Bugzilla look a lot better. Some usability improvements have been added, but overall, nothing fancy. Compared to Bugzilla, JIRA security risks are somewhat higher due to the larger overall complexity, a lot of client-side JavaScript code, and additional functionality provided by 3rd-party plugins.īugzilla user interface hasn't changed much over the years. Bugzilla team publishes security advisories and releases security patches in a very reasonable time.Ītlassian takes security seriously and publishes security advisories and patches when security threats become known. Third-party plugins can extend JQL functionality through custom functions.ĭue to full open-source code exposure and usage by Mozilla and some other big players, Bugzilla's security should theoretically be very high. JIRA lacks some of the expert-level search conditions that Bugzilla can do and searching for text in JIRA issues may be limited by how Lucene index works. The interface for writing a query is a text box with auto-completion and error highlighting, and is generally more usable than the large Bugzilla's form. JIRA has flexible JQL language (JIRA Query Language) that allows you to build arbitrary boolean expressions. Mastering all the options and understanding how Boolean charts work could be a challenge though. Excellent extensibility leaves room for a plugin that mimics Bugzilla's flags feature more precisely.īugzilla's advanced search is quite powerful, especially when it comes to all the options available in the Boolean Charts and high-precision searches like regexp matching. Labels in JIRA can be used as basic flags (without the assignment of a "?" flag). Migrating from Bugzilla security groups might be not an easy task. JIRA has more simple permissions model, more conventional and arguably more convenient. Security groups: quite flexible, but a bit mind-bending feature for grouping users & issues and granting permissions. As a general rule, Atlassian recommends not to store more than 200,000 issues on a single JIRA instance. Although you'd need more powerful hardware for JIRA, it will likely do well on a reasonably modern CPU and 1GB of memory. You can also keep multiple Bugzilla instances running on one server without much overhead.Ĭonsiderable – JIRA is a more complex system and typically executes a whole lot more of the server-side code per web request, so the server load is considerably higher ( but search in JIRA may be faster than in Bugzilla due to the Lucene index). On large databases (>100,000 bugs) the database may become the bottleneck when doing search queries. Low – Perl scripts act as simple CGIs and can be highly sped up with mod_perl. MySQL / PostgreSQL / Oracle / MS SQL Server Commercial (Source code available to commercial license owners)
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |