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."
"The most valuable feature is managing software development."
"Jira has been a good l tool for collaborating across large groups of people. The JQL feature is powerful and easy to use."
"The way it interfaces with Bitbucket and other things like that is valuable. Reporting and being able to link various issues or stories together are also valuable. We call them stories, and they're general reports."
"The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily."
"Jira as a structure has Confluence for documentation, and for what it is offering it is a strong suit with Atlassian."
"This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page."
"It is easy to integrate Jira within our current IT environment. Jira has connectors and supports various integration."
"We can create multiple boards for the same product backlogs."
"It should just have the integration with Jira. We haven't looked at it since Atlassian bought the product."
"Jira could be more, for example, like Micro Focus, which is what I mostly work with currently."
"For our company, we're thinking about not only project management solutions but also collaboration solutions, and maybe if Jira had a chart or quick commenting option, it would be great."
"It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins."
"Jira is raising their prices for the license, which is like a trap because many other providers offer services like Jira but for much cheaper."
"It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
"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."
"Jira required a significant amount of system resources, particularly for larger organizations with extensive workflows and numerous projects."
"When we use the plugin in Jira so, there are two different systems which we are working on, Jira and the X-ray plugin. The X-ray plugin should be incorporated into Jira because we have to fetch two reports. One report is faxed through Jira, and one can be faxed through X-ray. So there needs to be clarity about which the Jira team should reflect."
Earn 20 points
AgileCraft is ranked 18th 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.