Deployments in Jira - Understand what was shipped when, across any CI/CD provider

Hi Product Hunt! Taylor, one of the leads behind this feature, will add his thoughts later today. We know some folks have already started using this new view, and we're excited to roll it out to all Jira users. This is just one step in a long journey of making Jira the center of work for software teams. Let us know what you think! 🙏🏻 And read more here: https://www.atlassian.com/blog/d...

Hi Product Hunt! Our team is really excited to launch Deployments in Jira - an easy way for software engineers and everyone on the team to visualize and measure progress, from idea to production, for all the work in your project. For more details, keep reading! Many of our customers continue to adopt DevOps practices, specifically around better CI/CD capabilities so that they can deploy changes more frequently - making a faster feedback loop between your customers and your product development team. At the same time, we also heard that keeping up with all of these changes became really hard for the team to stay in sync and understand what features are being deployed, to who, and when. This feature helps solve exactly that! This builds on prior work within Jira Software that allows your team to automatically track deployment information tied to Jira issues. You do this by adding your issue key "ABC-123" to commit messages and PR branch names so that the CI/CD tools can communicate that back to Jira. This new Deployments in Jira view takes that information tied to each issue and gives you an intuitive, birds-eye view of all that work across the project. What's even more awesome is that this feature works with any CI/CD provider. Many of them are extremely easy to setup out of the box, which you can install the integration via our marketplace. Bitbucket Pipelines (of course!) but also Azure Pipelines, CircleCI, Octopus Deploy, Jenkins, and more. It is backed by a public API, so if you are using some BTF or custom tooling, you can send deployment information through the API and it will appear here. Lastly, for our premium customers, we’ll also be rolling out data-driven insights like deployment frequency and cycle time, to this view. These metrics, shipping in January, will help you understand the entire lifecycle of feature development - from idea to production. In the future we will be able to breakdown each segment of this journey to help you spot bottlenecks and areas for improvement (e.g. Is it your PR cycle time that's a problem, waiting for QA or design reviews, or moving from staging to production environments?). We’re looking forward to hearing everyone's feedback, and building out this new view and the capabilities around it. P.S. To turn on Deployments in Jira, just go to your Jira Software Cloud project, then project settings, then enable the "Deployments" option. It will then appear on your Project Navigation (left side). Don't forget to add issue keys in your commits as part of your development process, this is what automatically ties the information together, and your deployments will automatically update in this view.