We performed a comparison between IBM Engineering Workflow Management and Jira based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"Agile templates give us a standard methodology for every Agile project. Also, the ability to create our own object types and linkages to features/epics allows us to enhance the verification of feature readiness."
"Work distribution among team members and accountability for completion with a clearer picture."
"Traceability reporting is inbuilt and includes all your requirements."
"Good for managing stories, sprints, hydration and releases."
"We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data."
"I've never had a bug or a bug message that I needed to open a ticket for."
"It has enabled us to keep track of features or projects. Previously, we used to manually keep track in Office. We now have a centralized repository for all the information."
"The most valuable feature of this solution is the source linking on the commit level to git."
"The timeline management is great."
"It's a very complete product overall."
"We can create multiple boards for the same product backlogs."
"I like that Jira allows you to customize the flow for an agile process and adapt it to your own flow."
"The solution is extremely stable."
"The solution is very heavily vendor dependent."
"We have encountered issues with stability. We have seen where the entire system kind of goes for a toss when certain people use certain types of queries, which are very costly. Then the system kind of slows down a bit, and we have to monitor it."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"Some administrative tasks are difficult to perform. These could be simplified."
"Lacks ability to customize and reporting can be slow."
"Jira could be more, for example, like Micro Focus, which is what I mostly work with currently."
"It would be ideal if the solution could be available as a mobile application."
"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."
"The help desk and services management features are in need of improvement."
"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."
"The next-generation software projects lack a lot, and I found quite a few bugs. There are some really basic things that you still cannot do. For instance, to put a mandatory due date for a task that you create in one of these projects is still not available. That's a bit of a block because people, especially those who are not technical, are not going to add anything if it's not mandatory. It's going to be difficult to teach them that they should do it anyway."
"The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable."
"I don't know whether there is a Jira problem or a test risk problem, however, sometimes, we face issues on fetching the reports."
More IBM Engineering Workflow Management Pricing and Cost Advice →
IBM Engineering Workflow Management is ranked 10th in Enterprise Agile Planning Tools with 14 reviews while Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 243 reviews. IBM Engineering Workflow Management is rated 6.8, while Jira is rated 8.0. The top reviewer of IBM Engineering Workflow Management writes "Offers good traceability elements but UI needs improvement ". 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". IBM Engineering Workflow Management is most compared with Microsoft Azure DevOps, Codebeamer, GitLab, Polarion ALM and Endevor, whereas Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane and Polarion ALM. 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.