We performed a comparison between GoCD and Jira based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most notable aspect is its user interface, which we find to be user-friendly and straightforward for deploying and comprehending pipelines. We have the ability to create multiple pipelines, and in addition to that, the resource consumption is impressive."
"The UI is colorful."
"Permission separations mean that we can grant limited permissions for each team or team member."
"The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks."
"The solution is very scalable and flexible."
"We integrate Jira with QRadar which is helpful."
"This product provides you a good view of the status of your projects."
"The board has been a very valuable feature because it can be very simple for teams that are not technical. It can also be highly technical and have lots of data for teams that are technical. So we use it for both instances."
"We can integrate a lot of tools with the solution."
"I enjoy working with (and can recommend) Jira for a number of reasons. The best features are that it is friendly and provides good visibility. It's to the point and very effective."
"It's flexible and it can provide a lot of different options, such as dashboards, that you can create and manage."
"The documentation really should be improved by including real examples and more setup cases."
"The tool must be more user-friendly."
"The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us."
"Jira could be more, for example, like Micro Focus, which is what I mostly work with currently."
"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."
"Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon."
"Although it covers the overall requirements and measurements, it'll help if they had their own test execution feature."
"If they want Jira to be the one-stop shop of the view of all of your deliverables, not just from a defect tracking perspective, but also from a requirement perspective, a code perspective, and a testing perspective, it needs to pull out more data and work better as an integration tool."
"We're doing PI planning, Program Increment planning, and that kind of stuff, and it's not always a good facilitator for that. We tend to pull it out and put it into other tools to manage that, and then we get it back into Jira as that's our system of record for where all the stories are kept. That's probably the biggest headache with it."
"I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it."
"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."
GoCD is ranked 14th in Application Lifecycle Management (ALM) Suites with 6 reviews while Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews. GoCD is rated 7.6, while Jira is rated 8.2. The top reviewer of GoCD writes "User-friendly, useful multiple pipeline capabilities, and low resource consumption". 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". GoCD is most compared with GitLab, Microsoft Azure DevOps, GitHub Actions, Tekton and CircleCI, whereas Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM. See our GoCD vs. Jira report.
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.