<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow'>Customer Verified: Read more.</a>
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>Score 8 out of 101
Based on 1358 reviews and ratings
Likelihood to Recommend
JIRA is a perfect fit for any organization where they have a large "in-flow" of projects, tasks, requests, etc. It helps to visualize who and where the majority of the projects are and how much time is being allotted or can be allotted to a particular task. It is particularly helpful in making sure that each team member is given an equal amount of work (if that is the goal) and seeing where each project stands.
- JIRA is an excellent tool to connect different teams and work styles in an efficient way, without being too specific for some of them.
- It has a lot of features and settings to offer which really enable you to plan a task in a very detailed way.
- Thanks to the different conditions of a task, the status can be tracked easily and everyone always knows who's the one who has to provide input.
- Atlassian recently made a number of UI changes to both JIRA and Confluence. The Confluence changes negatively impact productivity by hampering what used to be a relatively straightforward navigation process. JIRA received an analogous set of changes; while less egregious, I find the new look increases my eye strain when trying to find needed information. New users may not have as much difficulty, but you should try it for yourself.
- Atlassian offers both a Cloud and on-premise solution; the Cloud version doesn't offer many customizations and plugins that are present on the on-prem (server) version.
- The amount of customization offered by JIRA is a blessing and a curse. Generally speaking, it's important to keep things as simple as possible; avoid adding custom fields or super involved workflows as much as possible (though the default workflow doesn't work in most situations based upon my experience).
- You'll need to nominate someone in your organization to own the JIRA effort -- this person should have a reasonable knowledge of JIRA administration but also have the ability to fairly present options and solutions as issues arise. If you don't have someone in this org but opt for a committee of sorts your instance can become a true mess and will negatively impact productivity.
Likelihood to Renew
Based on 33 answers
I do not make decisions at my new company, so it's out of my hands. I will say that we're in dire need of a new Project Tracking suite, but I'm not sure how interested they'd be in building something from the ground up. But, if discussions turn to blowing up our current solution and going in another direction, I will be recommending JIRA, and offering to take lead in it's implementation.
Based on 11 answers
Based on 2 answers
I used to get immediate support from the Jira helpdesk; also most of my issues are already explained in the user manual which is really helpful.
Based on 1 answer
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
I was not part of the team who decided to go with JIRA, however I have used Rally, Trello and spreadsheets and JIRA beats them all hands down. Rally was a good starter system, but they did not (at least at the time) have the advanced query and administrative/configuration features that JIRA has. Trello is a good team tool as well, but lacks a true backlog feature as well as advanced queries. Spreadsheets are great if nothing changes, so...
Return on Investment
- Better tracking of tasks/issues
- More accurate prediction of project completion dates
- Better task distributing
- Better task categorization
Premium Consulting/Integration Services—
Entry-level set up fee?