We performed a comparison between AgileCraft and Jira based on real PeerSpot user reviews.
Find out what your peers are saying about Atlassian, Microsoft, Nutanix and others in Application Lifecycle Management (ALM) Suites."The linking of PI Objectives with different features was one of the cool things. It had features, epics, and stories out of the box."
"We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there."
"The task management aspect of Jira is pretty pure. They have a lot of great plugins that really expand your options."
"What I really like about Jira is that it ticks off all the boxes for any agile project. It's easy to set up, easy to use, and it has excellent notification features. Jira is the top choice for anyone working on agile projects like ours."
"Great for tracking my development team's productivity."
"The traceability mapping feature is something that became very useful, especially during releases and bug fixes."
"We have found the structure, functionality, and how Jira handles the tickets most valuable."
"We use Jira mostly for task coordination and assignment. Additionally, scrum methodologies defined work items and bug issues. If we create any bugs all of them are fixed."
"The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on."
"It should just have the integration with Jira. We haven't looked at it since Atlassian bought the product."
"The dashboard reports can be improved. Its dashboard reports are good, but you cannot have complex reports. They are currently very basic. For instance, we can only choose two columns for a dashboard, so it is not friendly enough."
"We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product."
"I'm really new to Jira and I haven't used all of the features. However, it is quite difficult to use and manipulate. It was a little complicated for me and I don't know if it's difficult globally for others, but I had a difficult time understanding it at first. I used it for issues, epics, stories, tasks, and sub-tasks. For first-time users, Jira could be made better to help them understand."
"From a very software-centric or a lead developer standpoint, there should be the ability to work at multiple levels. You have epic stories and use cases or epic stories and tasks. It would be nice to be able to have multiple levels of stories and multiple levels of epics work with it. It's lacking a little bit there, and this is the big thing for me because it makes it difficult to do a real sprint when you're limited to one story per epic. It's really hard to isolate tasks at multiple levels to match the type of use cases you normally do. That's the biggest difficulty. Other than that, they've been improving year to year, and every version seems to have a level of improvement."
"There's a really steep learning curve for configuration."
"The performance is not so good sometimes. I know that fully depends on the implementation and the IT environment of Jira or the version of Jira installed. The performance is sometimes not so good. I would like to have a better response time from the Jira server. And it fully depends on the administration side of the Jira."
"It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira. I would like to have more reports in Jira. Currently, eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports."
"I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues."
Earn 20 points
AgileCraft is ranked 19th in Application Lifecycle Management (ALM) Suites while Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews. AgileCraft is rated 7.0, while Jira is rated 8.2. The top reviewer of AgileCraft writes "Linking of PI Objectives with different features was cool, but it didn't have integration with Jira". On the other hand, the top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". AgileCraft is most compared with Jira Align, whereas Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
Agree with Duane's comments for the most part. The two tools serve very different purposes. Where I disagree a bit is that Jira can be and is used by very large organizations to manage work. However Jira does not provide support for working across a set of related projects and services. This is what Agile Craft allows you do to - plus AC brings other capabilities like value stream management, a greater level of portfolio and business management, and management of delivery across a large set of programs.
It will definitely be interesting to see where Atlassian takes things.