Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
$81.85
per month 10 users
Liquibase
Score 8.3 out of 10
Enterprise companies (1,001+ employees)
Liquibase is a database change management tool that extends DevOps best practices to the database, helping teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database change management into their process than low performers. Liquibase value proposition: Liquibase speeds up the development…
There are many things done differently and in a smoother way when it comes to Liquibase. The CI/CD setup flow is easier. Switching between the different versions on different environments is really easy. The UI of login portal is user friendly and easy to use. Overall, it has a …
Liquibase is head and shoulders better than relying on SQL Compare alone for deployments. I haven't used Flyway, but based on our evaluation, Liquibase seemed to have a lot of functional overlap for considerably less cost. I would recommend the use of GitHub or Bitbucket in …
The Jira software works well for managing scrum boards and allocating resources to a task. When your Epics and Issues are set up properly, it can give you a good idea of where your team stands and the trajectory of your project. It is not the ideal solution if you need to provide documentation and support to people outside of your product teams or organization. It would benefit from having a public documentation or repository feature.
Liquibase is well suited when there is a need to manage database version. When there are database changes then Liquibase can easily manage, deploy the updates and it can build an automated CI/CD pipelines for databases. Liquibase is less appropriate where there is no change in database schema but that is less likely to happen.
Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9
We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase
Liquibase should rollback the if any one of the changes fails.
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.
We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.
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.
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.
The support is the only issue they took several hour to respond a simple EMail I believe that this is because of the Time Zone difference. By the time that they respond we already have solve our issues. Another issue is they close the support tickets some time before confirm that the question is solved. They are more focus in close tickets to reach the SLA that in give a real support
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.
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.
Jira Software has more integrations and has more features than many of its competitors. While some of its competitors do have better UI/UX than Jira Software, they have improved this greatly over time. Atlassian also acquired Trello years ago, so that adds better user interfaces to the system. They do also offer a pretty in-depth library of how to customize the platform that others don't.
There is no real competitor when it comes to what Liquibase does - at least not at the time we considered it three years ago. It was an easy choice in this regard, but we could have said no to it if it made our workload more difficult. But our proof of concept showed there were easy wins to be had by implementing its software.
