Atlassian Jira vs. GoCD

Atlassian Jira excels in complex software development projects and agile environments and offers robust tracking, customizable workflows, and integration with CI/CD pipelines. However, for small teams or non-technical projects, its intricate features and setup may feel overwhelming. Simpler task management tools may suit those scenarios better. Overall, careful tool selection matters.

Incentivized

Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.

Incentivized

• Running sprints and tracking progress of roadmap, epics, story, task and subtask
• The user interface is great. It allows tables inside details, have common shortcuts and clean design.
• Can create custom dashboards and can view data in multiple ways
• Advanced access rights based on role

Incentivized

• Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
• The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
• Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.

Incentivized

• Management of the software is very difficult at times, although has improved.
• Ability to manage resources is really non-existent, there are some plugins but they are ALL buggy (I've tested them all).
• Better integration with Trello, would love to see this happen. Right now it's very clumsy.

Incentivized

• UI can be improved
• Location for settings can be re-arranged
• API for setting up pipeline

Incentivized

This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.

In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.

Incentivized

JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.

Incentivized

Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.

One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.

Incentivized

Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.

Incentivized

Asana is great for people who need simpler project management systems. It does not have a wide range of features but its integrations are a lot more streamlined and easy to set up. Trello is great for those who just want to manage scrum boards and swim lanes.

Incentivized

GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.

Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.

Incentivized

• Jira has positively made our company's daily activities much better organized
• With Jira we can track progress and follow up on tasks
• Jira has great reporting tools which aggregate various data and give us a good overview of our teams capacity

Incentivized

• ROI has been good since it's open source
• Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
• More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date

Incentivized