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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
According to a recent survey we conducted, software & IT teams on average use 4+ tools to move code from development to customer-facing production. As a result, teams struggle with keeping the status of work updated and understanding the overall health of the delivery pipeline.
To solve this problem, we are excited to announce new integrations that bring up-to-date information from your favorite build and deployment tools into Jira Software Cloud. You can now use Jira Software to automatically update and track issues through your complete development pipeline, from backlog to release.
In addition to Bitbucket Pipelines, Jira Software now supports Jenkins, AWS CodePipelines, CircleCI, Microsoft Azure and Octopus Deploy.
These new integrations allow you to automatically pull in up-to-date build and deployment information on relevant Jira issues and expose key information about your pipeline across Jira issues, boards, JQL and via our newly published APIs.
Up-to-date information about your delivery pipeline is shown on the Jira issue. Need additional information? Use deep links to go from Jira Software directly to the right page in your dev tool.
This new information view is so powerful because historically it was dispersed across multiple tools only accessible to a few members of your team. Now anyone involved in the software delivery process can self-serve this information. For example, product managers, QA, and support teams can view which features have been deployed to customers and which are still waiting in staging environments.
With better information sharing between tools in your delivery stack, you can also improve cross-collaboration between teams. Teams such as QA and operations can collaborate in the software teams next sprint. For example, you can use build information in Jira Software to create a workflow between QA and developers and create a rapid feedback loop for testing at any point in your development process. For even closer collaboration, create test cases in Confluence and link them to your Jira issues.
Build powerful views into your development pipeline with support for JQL.
In addition to building better ways to collaborate, these integrations also give your team deeper insight into the development pipeline from within Jira Software. You can now create powerful views into your delivery pipeline with JQL queries across multiple connected tools. For example, you can write a custom JQL query to report all Jira issues that have been deployed to production but still have an open PR.
deploymentEnvironmentType ~ “production“ AND development[pullrequests].open
Visualize results on your dashboard, using custom filters (currently available in classic projects) or on advanced searches. One important callout here, the queries you see pull information from multiple connected tools, which is where the new power in JQL is stemming from.
We hope these improvements will give your team deeper insights into their development pipeline and save time spent on manual updates or context switching across tools.
If you are using Bitbucket Pipelines:
If you are using Jenkins, CircleCI, Microsoft Azure or Octopus Deploy:
If you are using AWS CodePipelines:
Looking to build a custom integration and publish it on the Atlassian marketplace?
Product Marketing for Jira Software
8 accepted answers