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."
"It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days."
"It's easy to use, and it also offers excellent notifications."
"With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board."
"The most valuable feature of Jira for sprint planning is the timeline feature, which allows for better visualization and planning of releases."
"Transparency of development projects, as well as approval processes for some business projects, has improved massively."
"I like seeing which tickets are open and what our response rate is. They have a lot of good metrics in their system to see what's going on."
"The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks."
"It includes by default all the necessary tools for a project manager to work and make their work more efficient."
"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."
"Could offer an improved user experience."
"Some of the interfaces, especially on the administrator side and for permissions, are not so clear. They aren't very user-friendly."
"They are not supporting in-house servers anymore and I think I've got until January to port this to something else."
"I also wish Jira had an indicator to tell you that you are approaching the limit for the story points that can be delivered during a sprint. I don't think there is an indicator like that, but such an indicator will be very helpful because then I will be easily able to see that we are approaching the limit."
"Backlog pruning and visualization are poor."
"Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
"Jira can improve by making user management better. It is not easy to have visibility of who has the right to do what. Only the administrator has this visibility but there should be the option for other users too."
"It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios. We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration."
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.
