Rate this page:
Connected Devops experiences with Jira
This page is a complete guide for Marketplace partners and customers who want to be part of the connected DevOps experience built around Jira as a work management hub.
In this guide, you’ll learn:
Why you should be part of the connected DevOps experience with Jira
How to contribute
What features Jira offers out-of-the-box that are powered by the connected DevOps data
How you can build new features to add value to the Jira offering
What the customer experience looks like
Thousands of software development teams use Jira to plan and track their work through the stages of the development lifecycle. These teams further use a disparate set of tools in their end-to-end software development processes. Setting up and scaling processes across these tools is complex and resource intensive. As software teams and their processes evolve, they want the freedom to choose products that are best for them, without having to slow down their innovation velocity.
Marketplace Partners and developers can leverage the following capabilities to connect their data with Atlassian’s data and build features that help teams manage their work across tools more efficiently with Jira as the work management hub:
Contribute to the connected DevOps graph
Consume connected data
Extend the offering with value added features
With event data sent in by first and third-party tools, as work progresses from idea to production, Atlassian builds out the ‘graph’ below that connects relevant entities together.
We continue to expand on these capabilities and the resulting graph by adding new APIs to unlock use cases with first and third party tools.
Why should you be part of the Jira DevOps experience?
See the table below for more on the benefits of connecting and consuming work management data with Jira. These featues are most relevant for Marketplace Partners, Platform Partners, enterprise customers and other developers.
| Value proposition | Connect your tools and data |
|---|---|
| Awareness and discovery |
|
| Seamless integration and on-boarding | Integrating with Jira allows your tools to have a friction free onboarding experience. The tools are then part of end-to-end software development processes that flow seamlessly across products from idea to production. |
| Out-of-the-box value-added features | In addition to the siloed tool specific features, your teams will also get access to cross-product Jira features including workflow automations, metrics, integrated search, and smarts that are unlocked by the connected data set. Teams that integrate their dev tools with Jira can leverage these features to improve their development velocity. |
How can you be part of this experience?
Capabilities to connect and consume the connected work management data are available through public REST APIs. You can start using the REST APIs below with Connect frameworks or use OAuth for self-hosted solutions.
Connect your data
These are some of the data entities that represent key elements of the software development process. Developers can use these APIs to send related event data and associate it with a Jira issue or a service. We capture this data, along with the relationships and build meaningful features with the connected cross-product data.
Remote links
The remote links API allows third-party providers to add a generic link through a public REST API and associate it with Jira issues or services. This is meant to capture a wide variety of non-specific entities like design, test reports, log files, or others that don't fall under any of the specific entity types.
Jira features unlocked by the connected DevOps data set
When you build a Connect App using above APIs and publish on Marketplace, you unlock the following benefits for your product and your customers.
Awareness and discovery
Public Marketplace listing 
Using our new DevOps APIs, you'll stand out from the crowd with custom
marketing labels, recommendations, and other tactics Atlassian uses to help
promote the SaaS partner that use our APIs.
In-product visibility helps with lead generation and visibility into your tool
to our entire Jira Cloud customer base.
Seamless integration and on-boarding
Jira site admins can simply click install to set up and provision the integration. There may be a few steps
to configure the integration post-install, but the ability for customers to see something they want and install it
immediately is a great experience.
Out-of-the-box features and value
Issue Detail View
One of the most viewed pages in Jira. Any DevOps data
sent to us will immediately display on the relevant Jira issue. They can click
on these items for more details 
DevOps detail dialog
Clicking a piece of data from the issue
detail view, teams can see some high-level detailed information. If they want to
know more, we help them navigate directly into the product (in this case,
directly into deployment #12). 
Navigate directly into the product
Clicking on key pieces of linked
data takes teams directly into your product where they can see more information
about that item.
In this example, Bitbucket Pipelines has decided to take
users directly to that deployment, and using the same Public APIs you have
available, to show the related Jira issues on that deployment.
Quick filters
Because you are sending the data format we
understand, this high-level data will automatically be available in Jira Query
Language (JQL), the search language in Jira.
Here, teams can create and apply search filters directly
on their board.
Global search
Teams can create their own search and
filters to find exactly what they are looking for, such as which issues have been
deployed to production but still have an open pull request. Or, which issues
have failed their deployments.
You could show this information back in your
own tool in whatever context you want. The information provided by you
is connected to Jira, and you have access to all Jira data as well.
DevOps automation
All the data we receive is automatically added to our Jira automation capabilities to help power more
automated workflows using the data coming from 3rd party tools.
Deployment View
Code in Jira
OAuth (2LO)
For teams who want to run some applications behind a firewall on their own self-hosted server, the Connect Framework will not be a good way to communicate data as it required teams to open up a port in that firewall.
With OAuth capabilities, Jira site admins can create an OAuth
credential and use that to send DevOps data in a secure way, without having to
open any ports in their firewall.
Same capabilities as above, highly
secure. 
DevOps metrics and insights
Customers that have linked their SCM and CI/CD tools will be able to view Cycle
time and Deployment frequency insights beacons on the Deployments tab.
Rate this page: