You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Thank you for joining our webinar, Optimizing developer experience with Open DevOps. We hope you enjoyed watching it as much as we did presenting it. If you missed it, want to share it with your team, or watch it again - here's the link to watch on-demand.
We’ve compiled the most commonly asked questions & shared our team's answers below.
We know you’re hungry for resources so here’s what we shared during the webinar (with a few extras):
Atlassian Open DevOps product information:
Product: DevOps best practices | Learn more
Training: DevOps Essentials | See curriculum
Articles & case studies:
Domino’s + Atlassian: Delivering technology - and great pizza - faster | Read now
Rent the Runway + Atlassian: Delivering a high-end fashion experience | Read now
NASA + Atlassian: Visiting Mars, courtesy of NASA | Read now
How Netflix does DevOps | Learn more
CMU DevOps case study: Amazon AWS | Learn more
Hertz turnaround plan | Learn more
Atlassian Survey 2020 - DevOps Trends | Download report
How can Open DevOps help us reduce error that go into production?
Atlassian Open DevOps integrates with all manner of CI/CD, testing tools, and feature flagging tools. Some examples include Zephyr, Xray, Mabl, Snyk, Sonarqube, Octopus Deploy, Jenkins, Circle CI, Harness, LaunchDarkly, and Split. Given the array of tooling available, it is possible to craft deployment pipelines to fit any use case. Jira software ties all of these tools together and provides easy access to the information you need through automation.
Customers have cited that having development information from the toolchain consolidated within Jira allows various departments to speak a common language and have a single source of truth, reducing overhead and management. Additionally, through Jira automations, not only are developers now able to get away from doing boring stuff – like manual status updates and manual testing – but also focus on fun, innovative developments. Our customers are able to deliver new, quality features, thanks to the consistency automated testing introduced.
How is Atlassian Open DevOps deployed?
Atlassian Open DevOps is available in the cloud only. Currently we do not have plans to release Open DevOps to Datacenter customers.
Integration across Atlassian suite
I already use Jira Software, Confluence and Bitbucket. Do I have access to Open DevOps? How do I integrate them?
Atlassian Open DevOps is a solution comprised of Jira Software, Confluence, Bitbucket, Opsgenie and integrations with best in breed 3rd party products. We offer tight integration of all of these products out of the box, allowing Jira to serve an a mission control center, or hub, across your entire development toolchain. In doing so, Open DevOps tackles the common, yet deep industry pain of a disjointed toolchain.
How does Open DevOps integrate with Agile/Jira?
Atlassian Open DevOps is a platform offering, where Jira Software sits as the backbone, or hub, of the development toolchain. As organizations integrate other Atlassian products or third-party tools, Open DevOps is able to serve as the single source of truth that not also houses, but also delivers relevant development information and metrics across the SDLC from Plan, Build, Test, Security, Deploy, Operate, Observe, and Continuous Feedback.
Nextiva is a fantastic example for how they leveraged Open DevOps to introduce DevOps practices to their already existing Jira instance and Agile practices. Read more here.
For now, we are stuck with SVN but we have Confluence, Bitbucket and Jira. Is Open DevOps still an option for us with SVN?
Open DevOps is available as a part of our Cloud offering. Although Bitbucket Cloud is not able to support SVN, you can read into how Jira can connect to other development tools here.
We're using Jira/OpsGenie/Confluence, but Gitlab instead of Bitbucket. Is Open DevOps still an option?
Definitely! Open DevOps is an open platform so we integrate with a long list of 3rd party tools, including Gitlab. We believe in enabling customers to connect the tools that work best for their team.
Open DevOps refers to the capabilities built around several of our solutions - Jira Software, Bitbucket, Confluence, Opsgenie, and the integration possibilities with other 3rd party tools. Because Jira Software served as the “backbone” or platform that connects Atlassian products and third-party tools, it is the only integration requirement to enjoy the features and benefits of Open DevOps: streamline development efforts, improve productivity and ensure efficiency of end-to-end development process. If you’re interested in more reading, we recommend this guide.
When you say Atlassian Open DevOps - is that all of the products coming together not just one product? It sounds like a collection of other tools. Is there something that lies on top or is it a tool unto itself?
Open DevOps is a bundled solution of Atlassian Cloud products – Jira, Confluence, Opsgenie, and Bitbucket – with Jira serving as the underlying platform that pulls DevOps data across the entire toolchain. With Atlassian, your DevOps toolchain isn’t limited to these four solutions. Open DevOps supports third-party integrations. Link any development tools, such as Zephyr, Xray, Mabl, Snyk, Sonarqube, Octopus Deploy, Jenkins, Circle CI, Harness, LaunchDarkly, Split and more. You also have the option to swap out pre-integration tools as well. For example, if you use GitLab instead of Bitbucket, you are more than welcome to swap these tools.
We already use Jira and Confluence. How do I also add Open DevOps?
You can get started with Open DevOps by first integrating these two solutions. We recommend reading the following guides to understand how to use the products better together:
To extract to full benefits that Open DevOps has to offer, we recommend, at a minimum, connecting your SCM and CICD tools of choice.
Can you integrate Trello and have all tickets show up the same way as it would show with Jira?
There are many integration options available between Trello, and Jira that support a variety of workflows. See this link for just a few of the options available.
We had seen Jira as a backbone, but how does Open DevOps combined with Team Central?
Today Open DevOps and Team Central do not integrate with one another out of the box, but they are complementary tools.
Open DevOps focuses on team dynamics and collaboration throughout the DevOps cycle through a mix of tools seamlessly interacting with each other. Essentially, it facilitates the “what” and “how” of what teams are doing.
Team Central, on the other hand, facilitates flow of information across an organization by tracking and reporting activities within a team. By providing a mechanism, stakeholders are kept up to date on what exactly the team is working on. Team Central also provides the ability to set and communicate goals. It facilitates the “why” of what teams are doing.
There appears to be overlap in features between Compass Alpha and Open DevOps. Any recommendations on how to bring the two together?
Compass is a developer experience platform that provides a unified real-time representation of the engineering output in one place. It helps you track the things your engineering teams build (components). It naturally complements Jira, which tracks the effort of your engineering teams in building those components.
You can consider Compass as a solution for implementing and tracking engineering best practices, have insights into the health of your DevOps, and a place around which you can build up a more sophisticated DevOps culture across your engineering teams. From that perspective, you can consider it as an additional element to the Open DevOps formula, that’s oriented more towards the technical/engineering teams.
What are the recommended DevOps tools? Jira in combination with Bitbucket?
Open DevOps is a bundled solution of Atlassian products: Jira, Confluence, Opsgenie, and Bitbucket. You are not required to use Confluence, Bitbucket, and Opsgenie to enjoy the capabilities of Open DevOps. You can integrate and swap with third-party tools as well.
To enjoy the benefits of Open DevOps, we recommend, at a minimum, integrating Jira with your SCM and CICD tools of choice.
Planning and Pricing
Does Open DevOps require additional licensing on top of Jira licensing?
The free edition of Open DevOps delivers Jira Software, Bitbucket, Confluence, and Opsgenie pre-configured out-of-the-box. It is free for up to 10 users on Jira Software, Confluence and Opsgenie; 5 users on Bitbucket.
Licensing for any third-party integrations would also be handled separately.
Ready to upgrade beyond Free? Pricing is determined by each Atlassian product you want to upgrade. When it comes to DevOps, you’ll find that the number of licenses you need from each Atlassian product – whether it be Jira Software, Confluence, Bitbucket, or Opsgenie – varies based on department need. In order to maintain this flexibility, pricing is determined independently of other Atlassian products you may already have.
Are the features in Jira, Confluence, Bitbucket, and Opsgenie considered "Premium" capabilities?
The features shown in the webinar are available in the free version of Open DevOps. All Open DevOps features are available to all editions. We do not have any “paid features only” for Open DevOps.
How do I check if my license already has Open DevOps?
All Jira Software Cloud offerings have access to Open DevOps. As soon as you integrate Jira Software - Cloud with other Atlassian Cloud products or third-party integrations (we recommend, at a minimum, SCM and CICD), you will be able to begin enjoying the features of Open DevOps.
Open DevOps is not a separate license you would purchase, but a capability that is available in Jira Software - Cloud when integrations with other tools are made. We recommend reading the following guides to understand how to use the products better together:
How do I stay updated on upcoming changes?
We have a public roadmap that is updated on a quarterly basis. This is available here.
Also in our Atlassian Community, see the DevOps collection under the Interests navigation. Whenever we're launching new experiences and features, we always publish a community post there.
Finally, we offer an in-product way to see what's available as well. Check out the features page, which is available in your project settings.
Support and Documentation Requests
Atlassian Open DevOps supports lots of good tools, but I can't find examples of implementations. I’m looking for end-to-end examples.
We’re commitment to helping users get solutions up and running quickly. We recommend reading these implementation guides for more info.
Environments vary across every organization, so setting it up in a way that works the best for you is an area we’d be happy to help. Don’t hesitate to reach out to your Atlassian solution partner or Atlassian support. Our partner vendors (i.e. Octopus Deploy, jFrog, etc) are able available for outreach to assist with your Jira integration needs.
Could I get a demo on how an Atlassian Open DevOps pipelines would work?
Bitbucket Pipelines is an integrated CI/CD tool built into Bitbucket. Here is a demo that shows how to push a change to production with Open DevOps and Bitbucket Pipelines.
We also recommend referencing https://support.atlassian.com/jira-software-cloud/docs/deploy-imagelabeller-with-bitbucket/ for a detailed explanation of how to deploy a sample project with Bitbucket pipelines. This article is part of a guide series that is found here.
Are there any documentation to help onboard developers new to Open DevOps.
Most certainly! We recommend reading this starter guide for Open DevOps. Additionally, please refer to here for a detailed guide on how to deploy a simple web service to AWS using Atlassian Open DevOps.
I want to demo those reports to my manager - Is there a video I can show them?
Is there support for setting up third-party software with Open DevOps or is support limited to the Community?
We’re commitment to helping users get solutions up and running quickly. We recommend reading these implementation guides for more info.
Environments vary across every organization, so setting it up in a way that works the best for you is an area we’d be happy to help. Don’t hesitate to reach out to your Atlassian solution partner or Atlassian support. Our partner vendors (i.e. Octopus Deploy, jFrog, CircleCI, Harness, etc) are able available for outreach to assist with your Jira integration needs.
Have questions or need help?
Are there Jira automations available for DevOps?
Yes. To browse the list DevOps of automation capabilities, view the DevOps section of the Jira automation template library here.
Are automations available in both the free and standard Jira Software versions? Does the automations feature require Opsgenie or any other integrations?
Yes, automations are available across all editions of Jira, including Free and Standard. No, Jira Software does not require integrations to access the automations feature.
Will automation rules take over for workflow transitions?
Yes, if you choose to do so, you can setup automation rules to handle workflow transitions. For more information, read here.
I want to have a CI job generate Confluence documents from Markdown in a repository so developer can maintain documentation like they maintain code. The API for Confluence seems great, but I’m having trouble finding an authentication method for my service. We are not allowed to use basic authentication. Help!
It’s worth highlighting that basic authentication is not as secure as other methods. We recommend looking into OAuth 2.0 method as an alternative. If you are experiencing any technical difficulties with setting any of those up, we recommend reaching out to our Support so the team can look into the specifics of your issue.
Please refer to https://developer.atlassian.com/cloud/confluence/rest/intro/ for a detailed discussion on the Confluence REST API and https://developer.atlassian.com/cloud/jira/platform/security-overview/ for a security overview.
Is it possible to deploy Confluence pages at the same time as a production deployment made through Open DevOps?
There is currently no built-in feature to create Confluence pages upon deployment, but considering the rich content that can be stored in a Confluence, one of the key questions to consider is the type of content stored in this automatically created page. Instead of automatically creating it upon deployment, you may want to consider building this manual step into your development workflow, so you can ensure that the right level of content is left behind, in order to have the most value for your users.
In any case, we suggest looking into automation examples we have in our library - https://www.atlassian.com/software/jira/automation-template-library/software-teams and https://www.atlassian.com/software/jira/automation-template-library/bitbucket-github-gitlab. In addition to that, you can expect some Confluence-specific automation coming soon, as per our Cloud roadmap.
We don't use any automated DevOps processes and really want to start. How would you suggest we start with Open DevOps?
The answer depends on the context of your organization and the type of work your teams are doing. We would encourage you to browse through some of the automation examples we have in our library:
Do you have a list of third party integrations?
While we don’t have a comprehensive list yet, here are a couple locations where you’ll see a comprehensive list in the coming months:
Can I deploy applications using Open DevOps to an on-perm server? To clarify, the intention is not to deploy Open DevOps to on-perm.
Yes, depending on your setup. You can deploy applications to on-prem servers if they are accessible from the internet. If not, you can look into Bitbucket Pipeline Runners, which allow you to run builds in Pipelines on your own infrastructure.
Can Cloud apps be integrated with on-prem seamlessly together under Open DevOps?
Unfortunately, there is no blanket answer for this question, particularly if you are looking for out of the box integration support. The answer depends on the on-prem tool that you are trying to integrate into Open DevOps. However, that’s not to say it isn’t possible. Integrations are conducted through APIs. Each integration requires its own application to be built for that purpose.
Do you integrate with Sharepoint for collaboration?
Today we do not support integration with Sharepoint for collaboration. Documentation collaboration is an active area that we are researching.
I communicate with my team members on Slack and Teams. Are there integrations with those?
Does the SCM used need to be on-cloud? What if we have an on-prem setup?
The SCM does not need to be on cloud. As long as you are using Jira Software Cloud, you have access to Atlassian’s Open DevOps. However, the more tools you integrate into your Jira instances, the more feature and benefits that will be accessible to you.
Can you link both Git and Bitbucket to the code section of Jira? We are currently in transition between the two.
Yes. With Open DevOps, you can link as many different code repository from various vendors as you desire.
Is there a version control mechanism?
Bitbucket is the Atlassian DVCS. You are free to integrate Open DevOps without DVCS such at Github, or Gitlab.
Are there any plan to have "Create branch" direct to the Github create branch UI if a Github repo integration exists?
Stay updated on upcoming features items with out public roadmap. The public roadmap is updated on a quarterly basis. This is available here.
Does Jira need to be integrated with Git/other code repositories to be able to get data on pull code, code submissions, etc?
Yes, this is correct. Today, Atlassian Open DevOps supports several SCMs including Bitbucket, Github, and Gitlab.
Does Open DevOps integrate with Bitbucket server running on premise?
Jira Software Cloud is able to integrate into Bitbucket Data Center. For more information, we recommend reading this guide.
Can we setup DevOps pipeline with Zoho?
Unfortunately, we do not support Zoho today. However, we are continuously exploring how we can expand our integrations support, and we especially love hearing directly from our customers. If there are integrations we don’t support, such as Zoho, let us know via the feedback mechanism in the product.
What specific tools does Atlassian Open DevOps support that are used to implement DevOps, like automatic builds and deployments?
Build automation is an active area that we are researching. Unfortunately, we do not support this category at this time, but do expect updates in the coming quarters.
For continuous deployment, we support Octopus Deploy, Jenkins, Github, GitLab, Circle CI, Harness, Codefresh, and jFrog. See the following links for more information:
Can I view deployments that are created by Azure DevOps? Is it possible to use pipelines in Azure DevOps pipelines but take full advantage of the Atlassian suite for everything else?
Yes. You will be able to view deployments data, created by Azure DevOps, in Jira. Absolutely, the philosophy behind Atlassian Open DevOps is to offer our users the flexibility to use the tools their developers love, all while having a single source of truth and single location to coordinate their toolchain. The only requirement of Open DevOps is Jira Software Cloud, which serves as the mission control center, or hub, for the developer toolchain.
Is it possible to connect Bitbucket deployments with 3rd party CD pipeline (e.g. AWS Code pipeline)?
Check out this Bitbucket documentation to see potential options.
Can Bamboo be used for deployments?
Today, we do not support Bamboo. However, we support the Bamboo integration with Bitbucket Cloud and Bitbucket Pipelines deployments. We suggest having a look to our deployments feature, that integrates well with other products such as Jira or JSM.
Does Open DevOps integrate with GitHub? We use Github actions with self hosted runners.
Open DevOps supports integration with Github. See here for a detailed example.
We use Octopus Deploy for managing our deployments and environments. Can that be integrated into Open DevOps to support those reporting features that were demoed?
Yes. Open DevOps supports integrations with Octopus Deploy. We are able to pull information from Octopus Deploy to show Cycle Time and Deployment Frequency. We recommend watching this video for more information on integrating Jira with Octopus Deploy.
Please note, an integration with an SCM is required to access these Open DevOps reports.
Github isn't listed in the CI/CD categories, is it really supported?
Yes. Github CICD is supported. For a detailed explanation of how to use it see here.
Can we integrate AWS and Atlassian? Meaning we make AWS changes and deployment directly within Jira?
We currently do not integrate with AWS. Integration allow users to see relevant context in Jira issues. At this time, Open DevOps integrations does not perform deployments or other infrastructure changes.
For CI/CD and automation we are using Jenkins, how easy is it to integrate in a way that we can have the deployment status displayed in Jira? Is there a good integration with Jenkins and it's pipelines?
Jira supports integrations with Jenkins. For more information Jira automations and Jenkins, we recommend viewing this video.
Are Tekton pipelines available as an integration? If not, is it possible to emit hooks to an URL to dispatch runs on any CI/CD system?
We do not support Tekton today. It is possible to emit hooks to a URL to report the builds & deployments from CI and CD systems respectively. See here.
We are using Jenkins to execute junits, and I want to know if Atlassian DevOps can be integrated with Jenkins, or is it required to build an Atlassian pipeline to each Bitbucket repository?
Jira supports integrations with Jenkins. You can take a look at our guide for integrating Jira Cloud with other development tools (https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-development-tools/) or specifically focusing on Bitbucket integration with build tools (https://support.atlassian.com/bitbucket-cloud/docs/integrate-your-build-system-with-bitbucket-cloud/)
Can I perform Canary deployments with Open DevOps and Bitbucket?
You can easily integrate with a feature flagging tool like Split, or Launch Darkly to get Canary deployments in Bitbucket. This is the benefit of Open DevOps. You can use best in breed tools to get the functionality you need. See: https://www.split.io/solutions/canary-releases/ and https://docs.launchdarkly.com/guides/best-practices/deployment-strategies
Canary deployments are not supported out of the box by Bitbucket. See here.
Does Atlassian Open DevOps support customer integration for vulnerability scan platforms?
Atlassian Open DevOps integrates with security testing partners such as Snyk, which does vulnerability scanning. With Snyk in particular, the integration happens with Bitbucket. For more information, we recommend reading this guide
Is there an ability to integrate with security CI/CD tools to make it Open DevSecOps?
Yes, definitely! You can check out examples in one of our DevOps guides.
Will you be integrating with monitoring software, such as New Relic?
Yes. Today we support New Relic, Datadog, Dynatrace, AWS Cloudwatch, Splunk/SignalFX. Application performance monitoring is an active area of research for integrations. See here.
Could you more explain about how observability will be supported by Open DevOps?
We are currently researching various tools under the Observability phase of the SDLC. Example tool categories include logging, performance monitoring, and error management. See the tools we support under each respective category:
Deployments & Releases
What is the relationship between deployments and releases (in the fix version field)?
Releases provide a way for you to group issues together based on the fix version field whereas deployments shows you which issues have deployments based on the data from your CI/CD tool. We show deployments against issues in the Release Hub as well as providing you the ability to filter the Deployments tab based on fix version. We are working on bringing these experiences closer together over the next year, so keep a look out for updates.
Some further detail on how Releases and Deployments work: The releases experience works by creating a version, assigning issues to that version via the fix version field and then marking that version as ‘released’ when the person responsible for that version deems that the work (issues) has been completed. You can also configure your Jira site to accept deployments from your CI/CD tool (Bitbucket Pipelines, Azure DevOps, CircleCI, GitHub, GitLab). These deployments are referenced against a Jira issue based on your developers including issue keys in your commits, branches and PRs. You can view all your issues with deployments against them via the Deployments tab in Jira Software.
What is Atlassian Open DevOps' experience with deployments that have a regular cadence in a regulated environment like healthcare? For example, in healthcare, you have to follow certain FDA regulations, which means extensive validation with every update. Curious to hear if there are healthcare customers who have been able to release features on a more regular cadence than every 4 months.
We don’t have any specific data points for our healthcare customers but there are a number of practices and process changes that can help you release more regularly. First up, we see customers starting to invest more in their testing process, specifically automating it throughout the entire software delivery life cycle which has become known as Continuous Quality. You can look at data around test coverage and work towards having high test coverage and insights around testing outcomes. Secondly, we hear from teams striving to release more often but in much smaller increments (batch size), this reduces the testing burden and limits the amount of change happening at any one time. The highest performers are releasing multiple times a day. This is achievable by having a robust testing process pre-deployment but also the monitoring and observability mechanisms in place to detect problems post-deployment. Lastly, more and more teams are moving towards a progressive delivery model as a way to separate a deployment from a customer actually seeing the change via the use of feature flags. This allows teams to constantly push out change and monitor their services and applications in production before making it available to customers. This is also a good way to group changes together. There are of course other options available to help release more regularly, such as baking in security checks at the start of development (concept known as shift-left) and setting up automated approvals based on pre-agreed checks, but the three things mentioned above are what we see the most. Hope this helps!
Does the "deployment view" roll up work done and deployed on a sub-task level to provide you a state of the parent story?
It currently does not. We have discussed providing a better sense of progress in the past by implementing a roll-up but we don’t have anything planned for this currently. We will take this under consideration though for future iterations!
Are the DevOps reports available to users that use Jira, but third-party products for SCM, CICD, etc?
Yes. As long as your third-party tools are integrated with Jira, you will be able to view these DevOps metrics and have a single location that houses development information across your toolchain.
What DevOps metrics does Open DevOps provide?
Today, we offer Cycle Time and Deployment Frequency reports.
If a development team has already set up a project but it does not have 'Deployment' in the menu (i.e. they used a different template) are we able to add it retroactively to their project?
Absolutely. Here’s the documentation on how to do this
Will the new DevOps metrics be available in existing projects?
Yes, these are available for all projects (new and existing). Here’s the documentation to help you set them up:
Can my team realistically apply DevOps practices even though we develop and support legacy programs in niche languages, not modern web applications? If so, how is the process different?
The high level steps of the DevOps process will be the same regardless of technology stack. The details of various CI/CD pipelines will be unique to the tech stack in question. Applying DevOps methodology to a large monolith application can be very difficult, but it is possible. The steps are the same. Test environments, QA environments, Production environments. Unit tests, integration tests, system tests. An automated CI/CD process. Recommendation is to start with automating the provisioning of Test environments, then building out a CI/CD pipeline to that environment. Once it's working, you can expand to a QA environment, and then Production once all of the issues are resolved.
We’ve found that DevOps practice you assume largely depends on how your organization is set up. In the case of Netflix and Amazon, they’ve been wildly successful with the NoOps DevOps team topology. However, it’s not going to work for every organization. We recommend referencing this link for the various DevOps topologies in the industry.
What are some of the DevOps metrics you recommend tracking to improve the processes?
DORA metrics are popular and used by DevOps teams to measure their performance. The four metrics are as follows: deployment frequency (DF), lead time for changes (LT), mean time to recovery (MTTR), and change failure rate (CFR). You can learn more here.
Do you recommend managing all code through a single repo or is it irrelevant? We currently have multiple teams and many repos but have often wondered if have one large repo would help coordination.
There are companies that have succeeded with single repo setups, and there are companies that have succeeded with multiple repo setupsThe best way to set up repositories varies from company to company. For example, NoOps teams have functioned successfully with multiple repos because they’ve set up the organization so that each team functions as a “pod”. To learn more on the various DevOps topologies in the industry, we recommend reading this guide.