We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"Work distribution among team members and accountability for completion with a clearer picture."
"Traceability reporting is inbuilt and includes all your requirements."
"The sprint tracking is really helpful and very convenient."
"It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing."
"It also works well with all the integrated tools that you buy."
"Jira as a structure has Confluence for documentation, and for what it is offering it is a strong suit with Atlassian."
"JIRA's technical support is absolutely fantabulous. I had used it in the past when I was working at my previous organization. And when we wanted to link it with a framework, they helped us out with the API we were looking for."
"Its integration with Bitbucket, Confluence, and other things is most valuable."
"The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out."
"In general, the GUI is nice."
"The solution is very heavily vendor dependent."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"In Jira, say on the team, no matter the methodology, it doesn't matter what I'm practicing, if I am using the tool for a while and I've compiled some sort of history. If I want to change my workflow, say my team is today using to-do in progress done, and tomorrow, I decide I want to use to-do in review and done, and I apply that new workflow, I have just now effectively lost all of my histories in terms of reporting."
"it would be helpful to have a better tutorial for learning and to have a better understanding of what the features are and what they do."
"Having more seamless integration with Confluence would really help us track our product management activity and other product details in one place."
"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."
"Could be more stable with more integrations."
"I think that there is some ease of use that could be brought in to improve certain things."
"Jira should allow you to create and develop pipelines easily. In India, we have to purchase them separately or integrate other data tools. All these tools should be in Jira."
"The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything."
"It's an expensive investment to make, so the decision should be driven on individual requirements."
"Licensing: The solution cost is high and should be brought down to increase competition."
"The ballpark figure is about $100 a month."
"If you are using just Jira, it is cheap, but if you start to use it and you feel you need some more services or more functions, then you have to buy add-ons, which can make it expensive."
"We are using the enterprise license which is nice because it ensures that we always have the latest versions of Jira software."
"Its price is fine, but we would like it to be less expensive. We are paying on a yearly basis."
"We had a perpetual license but have changed to a subscription."
"Its price is good and similar to other products. It is about five or six dollars per user."
"We have an enterprise license that includes cloud service and support."
"The basic price of Jira is reasonable, but for each plugin, we have to keep paying more. When you add it all up, it can be expensive. The main problem we face is we are forced to purchases plugin licenses for users who are not going to use them. For example, we have Jira licenses for approximately 450 people but if we only want a purchase a plugin for few people it is mandatory to buy the license for the 450 people who have Jira licensees. This is a problem because sometimes we need plugins for the product manager or for people in charge of the report, not everyone. For us, it can be very expensive in the end, they should alter this policy to allow plugins for only a set number of licenses."
IBM Engineering Workflow Management manages plans, tasks, the project status and acts as the critical link between required and delivered work. It provides flexibility to adapt to any process, which enables companies to adopt faster release cycles and manage dependencies across both small and complex development projects. This solution offers no-charge server software and flexible pricing models. It becomes a complete IBM Engineering Lifecycle Management solution—when purchased as a set of seamlessly integrated tools: IBM Engineering Workflow Management, IBM Engineering Test Management, and IBM Engineering Requirements Management DOORS Next.
JIRA has multiple deployment options to provide the flexibility your organization needs.
Cloud is a fully hosted service for customers who want to iterate quickly and have us take care of managing the infrastructure.
For customers who need to run our applications behind their firewall, we have Server and Data Center options. Server delivers greater capacity for a larger user base and gives you more control, allowing you to remain compliant with your enterprise IT, security, IP and privacy policies. For our largest customers, Data Center provides all the capability of our Server option, along with high availability, instant scalability and performance at scale.
Atlassian also offers premium support and strategic services for enterprise customers. Technical Account Managers are cross-functional technical advisors providing proactive planning and strategic guidance across your organization. Premier Support goes above and beyond our standard offerings to give you account-wide support from a team of senior support engineers.
IBM Engineering Workflow Management is ranked 12th in Enterprise Agile Planning Tools with 2 reviews while Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 116 reviews. IBM Engineering Workflow Management is rated 6.6, while Jira is rated 8.0. The top reviewer of IBM Engineering Workflow Management writes "Great inbuilt traceability reporting; unfortunately, the solution is heavily vendor dependent". On the other hand, the top reviewer of Jira writes "Great for collaboration, very stable, and extracting data is straightforward". IBM Engineering Workflow Management is most compared with Microsoft Azure DevOps, CA Endevor Software Change Manager, codeBeamer ALM, Rally Software and Compuware ISPW, whereas Jira is most compared with Microsoft Azure DevOps, Micro Focus ALM Octane, TFS, IBM Rational DOORS and Rally Software. See our IBM Engineering Workflow Management vs. Jira report.
We monitor all Enterprise Agile Planning Tools 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.