If you want other issue tracking systems, have a look at http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems - the comparison is handy and it's a pretty good long list
Benchmarking usually means looking at performance metrics, but those could be anything from end-user speed of response through to how much time your users spend on the tool. If it helps, the story I've heard was that JIRA was written because Bugzilla was getting in the way of developers doing real work, and it's grown from a simple issue tracker into a solution for all sorts of things. It's a lot more powerful and flexible than most other trackers out there, but it's unfair to try to compare with others in a vacuum - you really need to examine it in the context of which you'd like to use it. There have been times when I've recommended NOT getting JIRA because it's overkill, or simply not what the users actually needed. But you need to see their needs first.
Ah okay I see, because I have developed an interface using API JIRA REST, so I'll try to compare it with another tool according to following criteria such as: - The possibility of using the API which is not possible for another tool - Web service rest and soa - Integration of SLA and something like that
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs