Introducing Connections in Jira

Rachel Rafael

Note: this experience is currently in beta and only available to a small segment of Jira Software users. A little context Our team builds features that are powered by connections from across your DevOps toolchain. A connection is any type of container or object, such as a repository or build pipeline, that you can connect with your Jira project from another tool. Connections allow information to flow between your project and other tools and power several Jira features, listed below. At a high level, these features streamline work and improve collaboration by providing visibility and access to all your tools and generating valuable insights. Code displays repositories and links out to your source code management tools Deployments shows deployments over a timeline and generates reports on cycle time Project pages displays documents and allows you to create new documents On-call provides visibility into your team’s on-call schedule Until now, there has been no easy way to add and manage all your connections from all your tools. You had to manually add repositories in Code, documents in Project pages, and so on.   Introducing Connections This is the central place to manage connections from all the tools in your DevOps toolchain. This page is currently in beta, but eventually, you’ll be able to perform the following actions: Shipped — View existing connections in one place. Currently, you can view connected repositories and on-call schedules from select tools including Bitbucket, Github, Gitlab, and Opsgenie. Coming soon — Discover and add new connections that support your team. Eventually, you’ll be able to connect documents, build pipelines, feature flags, and more from a broad range of popular tools.  Coming soon — Install apps and enable features with a few clicks. Some connections require you to install an app or enable a feature. We’ll guide you through the required steps to get connected. Coming soon — Remove connections that no longer add value. Easily disconnect connections from your project. This won’t uninstall the app or delete any work from the tool. Exploring — Visualise your tool coverage across the software development lifecycle. Understand the gaps in your process and toolchain, and identify the various tools in which your team works.   Tell us what you think in the comments We’d love your feedback so we can build the best experience for your team. What’s missing from this experience? What do you think is most valuable? What tools and information do you want to connect? Anything confusing or unhelpful?

Jeanne Howe_56oel8

To add something along these lines to a Jira project MUST allow for Admin configuration. The Admin MUST be able to turn on/off this feature. As a "regulated" house, we can not allow our end users to simply connect into any app they want. All apps must be validated before they can be used and re-validated on each release. 

We also standardize on the tools we use and integrate with Jira, so allowing a team to connect and use a tool outside of our standards can not be permitted.