Atlassian Jira is a project management tool, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
$9
per month per user
IBM Cloud Continuous Delivery
Score 9.9 out of 10
N/A
IBM Cloud Continuous Delivery, available on IBM Cloud, allows users to provision an integrated toolchain using customizable, shareable templates with tools from IBM, third parties and open source. Automate builds and tests with Tekton-based delivery pipelines, and control quality with analytics.
$0
Pricing
Atlassian Jira
IBM Cloud Continuous Delivery
Editions & Modules
Standard
$9
per month per user
Premium
$17
per month per user
Enterprise
Contact Sales
per year
Lite
$0.00
Professional
$35.00
Authorized user per month
Offerings
Pricing Offerings
Atlassian Jira
IBM Cloud Continuous Delivery
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
Higher volume teams may qualify buyers for a discount.
Compared to gitlab, Jira offers a lot more features and details. The gitlab feature is nice for small projects or teams but we are multiple teams with multiple topics and projects even inside one team - so Jira is more applicable for our case. Azure DevOps offers a comparable …
Performance and features compared to other tools here are really impressive and its very easy to use and it has very good support and it can do majority of tasks like Task ManagementResource ManagementWorkflow AutomationSupport for Agile MethodologDocument ManagementChange …
Jira is more feature-rich than Trello and also has better integration with other tools. Trello is a lot more focused on work tracking, while Jira can do a lot more than that. Both can also be combined, although they're often considered mutually exclusive alternatives—I've seen …
Trello is amazing for simple project management and great for non-technical teams, but it lacks the depth and complexity of JIRA for detailed issue tracking and complex workflows. Asana, similar to Trello, is great for simple and lightweight project management but isn't …
Atlassian Jira is like an old person trying to look young. In the last couple of years it started succeeding somewhat but I'd still pick something from the alternatives if starting a new project.
Atlassian Jira provides the greatest access to integrated tools, the most common/familiar interface and toolset for most development teams, and is competitively priced when compared to the level of customization required to outfit similar tools we've used.
Monday.com cannot be integrated with CI/CD tools, whereas Atlassian Jira integrates with CI/CD tools seamlessly. Atlassian Jira has strong Agile and Scrum support. Coming to Monday.com, it has basic agile functionality. But Atlassian Jira has a complex UI, and Monday.com has an …
Atlassian Jira integrates with the other Atlassian products, like Confluence and Trello. Atlassian Jira makes it easier to collaborate and keep track of everything.
Atlassian Jira is a very different tool than opsgenie and Confluence. Opsgenie excellences in the current work in progress and visualizing the trends of how the work is getting done, but it really doesn't function as a longterm repository of a knowledgebase, instead that is …
I have majorly used Atlassian Jira and not Asana as i have only worked it for like a month or two. The vast support with Confluence and bitbucket makes Atlassian Jira my first choice among all other major player who are competing against each other. I absolutely love using …
Jira was selected because it is used by all of our clients and has become the accepted standard in the type of work that we do. The other tools are great in their own right and would better suit a more insular way of working, where a business conducts all work internally, but …
We've used a variety of tools for project/work tracking and Jira seems to be the most detailed one that allowed cross-functional collaboration between product, dev, ux, and other key stakeholders. It also allows users to be tagged in work and asynchronously share documentation …
Jira was the application choose by the company that work for, was already part of the culture, it perform well for organizing and managing the software projects and the company, ClickUp its easier to configure projects and automations and Azure Dev Ops and Trello is simpler but …
I didn't pick Jira, it was imposed to me from my employer. If it were for me i would probably have used Linear, since i think it's much more streamlined and doesn't really have tons of less features, but rather an extremely simplified interface that can even work perfectly as a …
I may not have the correct Salesforce product name but we used their version of break fix and project management and it worked well out of the box. I thought that part was called Remedy but something else came up in the search. For Confluence we like it for sharing documents …
Asana was less robust. It is lightweight and has a lot of the same features, has better visuals but it always feel like it isn't robust enough. It is straightforward but it doesn't have the bells and whistle a more robust system like Jira does. And it doesn't have as much of a …
Best fit for IBM Cloud and IBM Hybrid cloud strategy. Very well suited for RedHat Openshift and cloud-native build packs. Complementary solution for Enterprise Java workloads transformation and modernization journey such as java microservices development lifecycle and also …
We chose IBM Cloud Developer Tools for multiple reasons. Cost, current infrastructure vendor list, and Cloud Operations team experience were key driving factors for us. Palo Alto's Prisma Cloud product was slick for sure but we found it more difficult to deploy and integrate …
IBM Cloud developer tools had good support for mobile and web based applications and seemed relatively easy to integrate to our applications. We have other IBM tools so it had a slight edge over others when we compared.
IBM Cloud Developer Tools stack up against Visual Studios and other integration suites, with an agnostic approach. IBM Cloud Developer tools integrate seamlessly with your existing stack to augment and accelerate data science and analytics projects at large. Tools are designed …
This is recommended over other applications as it has a continuous delivery for non-mission critical applications also which has simple proof of concepts and this is reliable. Also, the integration to different platforms along with cloud implementation is an add-on. The ease of …
IBM Cloud Developer Tools is way easier than Jenkins and most of the features Jenkins has are not useful for us and the features we wanted were absent ButIBM Cloud Developer Tools saved our lives and is perfect in all aspects as we can easily develop and deploy. The only thing …
Both competitors listed work in a similar manner; you can automate the deployment of servers using configuration files and the command line. The difference is that Ansible and Terraform are provider-agnostic, meaning you can use them for other hosting providers as well (AWS, …
Mainly, AWS offers 5G services which are futuristic. AWS has More products than IBM Cloud & it offers High Parallel Performance & Computing. Better global coverage than IBM Cloud & Rigid SLAs with credit compensation
Coming to Microsoft Azure, its user interface is very easy to …
Eclipse with IBM Cloud Foundry and Kubernets we used to develop application in on premises and deployed into the cloud. And we created containers, created many projects and deployed into the cloud by using Continuous Delivery in IBM Cloud. Great service and great support. IBM …
There's not really a technical background on the decision of using IBM Cloud Continuous delivery. Our CTO assisted to a conference where IBM was promoting their services and offering a free tier. As in that instance the company was starting, every free tier offering was well …
CI/CD is much more user friendly than Jenkins. It better integrates to IBM Cloud features. On the other side, Jenkins deployed in a VM or better, on a K8S cluster is a less expensive solution.
I find IBM Cloud Continuous Delivery service way easier to set up compared to Travis CI. The visual interface helps you navigate throughout the service effortlessly. I used Travis CI 2 years ago, although it wasn't complicated, I took more time to create and set up an instance …
Jira facilitates software development, bug tracking, and sprints. It's ideal for structured workflows, issue management, and customer communication. However, more straightforward tools might be more efficient for highly creative, unstructured tasks or tiny, agile teams with quick visual overviews. Jira's complexity can be overkill for basic task lists.
It provides a cloud-based integrated development environment that integrates with other IBM Cloud services to provide a streamlined development workflow. This includes real-time collaboration and code sharing capabilities, making it easy for teams to work together on projects. This feature is very useful for our app to maintain the code
JIRA is highly integrated into our organization. Nearly every department uses it, and many have multiple JIRA projects set up to track different types of work. We rolled out JIRA in a staged manner, but it continued to be adopted by more and more people and departments because it continues to show results. I expect we will continue to renew our JIRA license for years to come
It's a great platform to develop, run, test and deploy the applications easily. And it makes very easier and secure the implementation of continuous delivery process. For first time and experts also can use this service so easily. Great service provided by the IBM Cloud Continuous Service. There are more services that helps a lot to work on it. Thanks a lot.
Atlassian Jira is relatively easy to use, but there are several ways to configure it, which can make it more complicated if you configure it incorrectly. Keeping the customizations and complexity limited to being the project would be suggested to ensure you don't lose in-built Atlassian Jira features, then change the configuration as you find things aren't meeting your exact needs.
Did not face any issues and whenever they plan maintanance they update all of us very well in advance also so in that view we are good with the product stability.
Performance is really good though it holds lot of data it loads quickly especially search operation also get the results very quickly as needed hence its good
I have not had a chance to contact JIRA's customer support. It does offer extensive documentation, although it often feels too technical for me. There is also a JIRA training app that lets you take little lessons and quizzes on different areas (e.g., JIRA basics, agile). I did find it a helpful way to teach myself.
In more than a year using the IBM Cloud Continuous Delivery tool, I haven't had any major complaints or problems. However, in the last month, IBM suffered from a couple of problems through several of its services, and for a short period of time, I couldn't deploy successfully my projects. The problem was brief and was quickly fixed.
Had received training from our own internal user so it was good and also very easy to understand topics and many tasks in the UI are self explanatory and we can do by our own
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 is more feature-rich than Trello and also has better integration with other tools. Trello is a lot more focused on work tracking, while Jira can do a lot more than that. Both can also be combined, although they're often considered mutually exclusive alternatives—I've seen cases where companies choose to use either one or the other, but I haven't met an actual case of a company using both.
We chose IBM Cloud Developer Tools for multiple reasons. Cost, current infrastructure vendor list, and Cloud Operations team experience were key driving factors for us. Palo Alto's Prisma Cloud product was slick for sure but we found it more difficult to deploy and integrate with our current environment and applications
JIRA has increased the teams' productivity and efficiency; the sprint timelines have improved by 15-20%.
JIRA's integration with tools like Bitbucket and Confluence has improved functional collaboration, leading to faster decision-making and issue resolution by approximately 10-15%.
Additional functionality requires additional third-party plugins, which require additional costs; the requirements of these plugins increase the costs by approximately 15%.