Our mission is to unleash the potential of all teams through the power of collaborative tools and practices. This is especially true for teams practicing DevOps, where a good tool can really improve collaboration between the development team, IT operations team, and business team.

However, increasing the collaboration of multiple teams may also impose other costs on developers. While developers don’t have to write code and build innovative solutions, they end up spending a lot of time integrating multiple tools, updating their status, and sharing it with other teams.

This was evident in the DevOps trend survey we conducted earlier this year. What we found was that what was supposed to make developers’ lives easier actually caused new pain. Too many incompatible tools, manual process management, and changing collaborative practices are hampering developers’ desire to implement full-link DevOps.

Ninety percent of the teams reported that DevOps had a positive impact on the business, but were also likely to waste time on innovation, and 84 percent said they faced implementation obstacles.

Recently, we introduced 12 new features for DevOps, whose automation and integration capabilities help developers save time and deliver better code faster. ** Developers can have fewer context switches, fewer meetings, and fewer IT alerts about security events. As a result, developers will have more time to code and create value for customers.

Our new automation capabilities integrate Atlassian products with third-party tools, allowing the development team, IT operations team and business team to work together effectively to help developers focus on their code. Atlassian uses JIRA as the foundation and ultimate fact source to unify all DevOps efforts and reduce the collaboration burden.



You can plan and track projects without switching code contexts

In our opinion, the DevOps toolchain is not a one-size-fits-all solution. DevOps is a toolkit that spans different applications and teams, and developers have the best idea of which tools to use or how many to use. But just because of this flexibility, how to effectively coordinate between teams becomes very urgent. Our survey found that an increasing number of DevOps teams say they need more than five tools to keep track of project status. IT operations and business teams that do not work closely together using these tools also need to understand what is happening and when. This is where JIRA comes in. JIRA can automate the unification of work across teams and tools.

We’ve built deep integration between the JIRA Software Cloud and Bitbucket Cloud, GitHub, and GitLab to enable issue tracking and project updates where you automatically code them, without having to go back to JIRA. Your project manager will not need to remind you to update, nor will it interrupt your coding process, because your project committee will automatically update based on your work in Bitbucket, GitHub, or GitLab.

  • The new “Your Work” dashboard in the BitBucket Cloud has been expanded to include the JIRA issues assigned to you, so you can quickly move from one task to the next without jumping between tools. In each library, you will also soon see a new team-level view in the JIRA Issues TAB to view associated projects and issues.
  • In Jira Software Cloud, we have enhanced the Automation functionality with the powerful new Devops Automation Triggers. With just a few clicks, you can create automation rules to keep your work in sync with development activities, triggered by Commit or Pull Request activities in any connected code base. At its most basic, you can automatically update the status of related JIRA issues, and these new automated approaches also allow for more complex rules, such as reassigning JIRA issues for quality checks or code reviews, or even sending messages about new PR to your team’s Slack channel. These automation rules can be used with Bitbucket Cloud, GitHub, GitLab, and any codebase that integrates with the JIRA Software Cloud.



Review, test, and deploy code without switching tools back and forth

Every team wants the best tools for writing and reviewing code, and with BitbucketCloud, we have everything you need. We want to maximize the productivity of developers in their daily work, which is writing and reviewing code.

Whether you prefer working in BitBucket or in an IDE, our goal is to get you on the right track and reduce unnecessary back-and-forth between tools.

  • BitBucket Cloud’s new Pull Request experience provides you with an innovative design that makes it easier and faster to view code changes. New features such as consolidated task lists, integrated JIRA issue creation, and active feed filters enable developers to complete their code reviews faster and efficiently handle multiple extract requests at once.
  • Atlassian VS Code Integration brings the entire development Pipeline to your editor, view the task list and experience the full code review process in JIRA Software Cloud, and CI/ CD in Bitbucket Pipeline.

Deliver quickly and flawlessly

The DevOps team is trying to speed up its delivery process by automating and moving manual checks of “shifting left” into the CI/ CD process. To address this issue, we introduced problem scanning and quality reporting into the BitBucket Cloud code audit experience so that reviewers are alerted to potential issues before pushing anything into production. You can also try out our new automated change management feature that connects your CI/ CD process with easy change approval in the JIRA Service Desk Cloud.

  • Code Insights in the Bitbucket Cloud allows you to bring the best DevOps scanning, testing, and analysis tools to your Code review process, including MABL for automated testing and Sentry for automated monitoring. Our new DevSecOps integration with Snyk is particularly important because Snyk can scan and highlight important security vulnerabilities early — before they become SEV-1 security events. All of these integrations are based on open APIs, so you can extend the BitBucket Cloud with other code reports from your own tools.
  • Using JIRA Service Desk Cloud and Bitbucket Automated Change Management A command of JIRA Service Desk Cloud and Bitbucket (currently in early access) will pause your CI/CD process to create change requests in the JIRA Service Desk, Then trigger deployment after approval:
  • Our risk assessment engine in the JIRA Service Desk Cloud quickly evaluates the risk of changes and automatically approves and deploys low-risk changes.
  • Our Change Management view in the JIRA Service Desk Cloud simplifies the approval process for high-risk changes by aggregating all the information into traceable change requests so that teams can review and approve them manually if necessary.
  • Automated change management capabilities support Bitbucket Pipeline, Jenkins, Circle CI, and Octopus Deploy.

Reduce the alarm load and resolve incidents faster

When an incident occurs, the key to solving the problem quickly is to quickly determine the cause of the problem. As your team adopts DevOps and automates their deployment process, change-related failures are becoming more common. Wouldn’t it be nice when you start working on a failure to know if the most recent code change caused the problem, and to be able to get help from the right developer immediately?

For most teams today, this requires advanced instrumentation, including checking Git history and JIRA work orders. We know there has to be a better way. OpsGenie’s new deep integration with the JIRA Software Cloud and Bitbucket Cloud helps teams streamline the entire process by providing first-timers with an audit trail of recent deployments and their associated JIRA work orders.

  • Our OpsGenie and Bitbucket Cloud integration centralises all alerts and filters out noise to ensure that the right issues are found, the right people are warned, and the right actions are taken. Using the Incident Investigation Dashboard, the team can look at the deployment before the event occurred, add it as a potential cause, and then contact the developer who made the change so that they can roll back and resolve the event.



DevOps success depends on tools, practices, and culture

A successful DevOps implementation is not limited to perfecting connectivity tools. Most DevOps practitioners agree that they see people and team culture as the number one factor for a successful implementation. To strike that balance, we’ve created a new place for you to learn and share DevOps best practices.

Our resource center provides guidance on how to connect tools to practices and how to foster a world-class DevOps culture. The Centre includes:

  • DevOps Community (Exclusive AMA with DevOps Thought Leaders)
  • DevOps Confluence Template (to improve DevOps habits and set long-term team goals)
  • DevOps guide (knowledge on how to link tools such as JIRA to industry best practices such as CI/CD)

We also extend automatic integration to your common communication tools. For your day-to-day work, our Slack integration and StatusPage integration can help you adopt DevOps best practices in your internal and external communications.