Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
For most bug tracking systems, it stacks up pretty well considering the cost (it's free). But for a little investment, you can license JIRA which is far superior.
Bugzilla is affordable and easier to use by newly forming team or group in our organization. As the team grows bigger we still continued to use Bugzilla as it is comfortable to use. We tried JIRA tool for bugtracking but it was expensive when compared to Bugzilla so switched …
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but …
Bugzilla had many of the same common features necessary for bug tracking. However, the ease of use that JIRA provides while abroad is essential for many companies, and is the ultimate decision maker for those establishments. Additionally, while bugzilla includes a time setting …
Bugzilla is very easy to use, very intuitive, and user friendly! For agile projects, the Kanban is very useful and you can drag and drop the defect to change his state. I work 10 times faster with Bugzilla.
JIRA from Atlassian, Quality Center from HP, TRAC were a few other tools that we had considered. The core features are present in almost all the competing tools. Bugzilla may not have a user interface as good as other tools, but serves the purpose very well as a bug tracking …
Bugzilla would be useful if you don't want to pay for bug tracking but maintenance is a bit painful. We are using Gitlab as our repo, The way Gitlab is progressing, I think We can replace Jira with that.
Overall JIRA comes across as a clear winner. Perhaps the only close competitor is Bugzilla since it is open source and has a lot of other features that have been built for it, even if by many different teams.
There are two advantages that Bugzilla has over JIRA: 1. Being open source (read free) 2. Having a feature that few of my users desperately need: clone a issue to multiple projects at once
Trac is as basic as the subversion with which it's often associated in feature set, requires signifiant time and patience to set up much less customize/configure, and is being abandoned by most industry folks. Bugzilla is a classic solution which holds up, but has an interface …
I've used Trello for managing tickets, it's possibly but provides no ability to have backlog features unless you use plug-ins. Plus, once you get a large backlog the page takes a long time to load. Jira is quick and has this all built in.
Jira Software is a much more robust solution that offers more features than the alternatives. Since our engineering department is also using BitBucket, it makes the choice easy to go with the whole Atlassian suite.
With easy customization, JIRA was able to scale up to our varying organizational needs. We did not have to buy separate tools for Bug life cycle management, customer support, product delivery, or project management. Nor did we build any other in-house solution. It spans to all …
Flexibility. Our teams use JIRA in many ways and we've found it to be up to the challenge in nearly all cases. I would easily recommend JIRA to a company of the right size and complexity. It just may be overkill for teams that need only light project tracking and to-do lists.
Jira provides the full agile model with a customization path. Moving from road-testing to driving it on the highway is a short learning curve. VersionOne is more complex.