Open DevOps

The feature of Open DevOps that I enjoyed the most was its versatility. It gave me the freedom to adapt and adjust my infrastructure to meet my needs while enabling me to swiftly design, deploy, and manage cloud-based applications. Because to Open DevOps' open source nature, I had access to and control over the platform's source code, which allowed me to adapt it to my unique requirements. The platform also offers a vast selection of tools and services to facilitate and speed up development and operations. In conclusion, Open DevOps offers a practical and successful method for creating, deploying, and managing cloud-based applications.

It was a little tough for me to browse and the interface was a little perplexing. The resources and choices I required to handle my projects were hard to come by. I also thought the pricing structure was a little difficult to understand and a bit confusing.

Once set up, it is easy to use and offers a lot of options to customize it to our processes.

JIRA is very difficult to set up and configure correctly. Support is inexistent. In one instance, an issue got deleted by some JIRA quirk, we lost all billable time tracking associated to the issue and JIRA never even tried to investigate or let us know what happened or what we could do about it. There are also outages on a regular basis or parts of the system not working, or working differently for members of the same team.

Jira is out of the box free, and it's amazing because it works with everything by the same company. It also allows for easy organization of projects and silos, which intersect with each other. You can easily hand off tasks and allow people to collaborate.

Jira has a very development based angle, so if you're trying to manage a hybrid team, it works well. But if your team is marketing heavy, it's very anti-user friendly unless a person has familiarity with code or databases. It's just sparse and less user friendly.