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 UI is colorful."
"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."
"Permission separations mean that we can grant limited permissions for each team or team member."
"JIRA stores history of changes, which helps a lot to track who, when, and why the issue was modified."
"Jira is very useful for project management for internal projects."
"Being able to automatize the deployment of the solution has been great."
"The solution offers a lot of plugins."
"I like the test cases in Jira. The orange dash items view was great, and I like the features and layout of the data. It's quite different, and people are now getting their items so quickly."
"Workflow administration is an easy process, especially with respect to defects."
"The workflows are very easy to handle as far as scalability goes."
"I think one of the most powerful features in Jira is the customization of fields and workflow."
"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."
"It would be very practical if you can more freely reach the information that is already inside the system. Currently, we have to buy add-ons for it. There is a lot of information in the Jira system that you can handle only through add-ons. You cannot reach such information on your own. If you want to use this information, which is already in the system, you have to buy some add-on to use. For example, information about how much time an assignee is spending on a ticket is there in the system, but you cannot access it without an add-on. JQL is a very good way to reach the data inside Jira. If we can reach more objects, even through JQL, it would be great."
"The automation feature needs to be more user-friendly."
"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."
"The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable."
"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."
"Jira lacks easy capacity calculation compared to TFS, making it harder to know how much work to allocate to each specialist."
"Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it."
"The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again."
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, Tekton, GitHub Actions 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.