Atlassian Open DevOps: new toolchain page launches in Jira Software

August 9, 2022

With the latest feature releases from Open DevOps, Atlassian aims to equip software teams with the tools they need to get the job done, together. This blog contains details on the latest Open DevOps capability: toolchain page.

Got questions or need help? Comment below!

Tool sprawl limits developer productivity

The average software company uses 25 tools in their software toolchain. This means teams wrestle with a complex and disjointed array of tools. This causes a lack of visibility into the software development lifecycle (SDLC), breakdowns in team communications, and silos. That's why while many teams see gains from adopting DevOps, 84% still face implementation barriers.

Software teams feel that standardizing their organization's toolchains is the only way to alleviate these pains. However, standardization comes at an unspoken cost. When we don’t support individuals and teams to work creatively, we stifle innovative ideas.

Introducing Open DevOps and the toolchain page

Atlassian introduced Open DevOps to uniquely connect software teams with new ways of collaboration across projects and toolchains. Open DevOps is a platform powered by the integration of Jira Software and your team’s favorite tools. By connecting disparate tools, Jira Software becomes the mission control center for your software toolchain, giving teams the extensibility of a custom toolchain and the coordination of an all-in-one solution. All users of Jira Software Cloud have access to Open DevOps features, regardless of license tier. Start by integrating your source code management (SCM) and/or continuous integration continuous deployment (CICD) tool of choice into Jira Software (see sections below).

Today, we have two exciting updates that further strengthen our Open DevOps offering.

First we’re announcing the release of the toolchain page, a project administrator experience that makes it possible to discover, connect, and visualize toolchains, all within Jira Software

Access the toolchain page under Projects > Project settings to begin exploring the DevOps possibilities for your teams. With the new toolchain page, development teams can now…

The toolchain page is available today to all Jira Software Cloud users. For more information on how to add an application to a project, view this demo.

Next we’re announcing the latest expansions to Open DevOps integrations

When we first introduced Open DevOps, we also shared our commitment to helping our users leverage the best tools for the job. We helped users connect their SCM and CICD tools to Jira, allowing software teams to gain end-to-end visibility into development in progress, all within a single location.

Now, Open DevOps supports all stages of the software development lifecycle (SDLC) end-to-end, allowing software teams to gain visibility into the entire lifecycle of a feature across all eight phases.

blog-header-1120x545-toolchain-devops@2x.png

In the Discover phase, software teams collaboratively explore what to build. Through diagramming tools like Miro and Jira Product Discovery, teams can organize and prioritize ideas, then convert team favorites into Jira issues to share context into the genesis of ideas.
In the Plan phase, teams align on project plans for the upcoming sprint. Tools like Figma and Confluence bring feature requirements to life through user stories and prototypes. By attaching them to issues, Jira Software facilitates a seamless handoff between product, design, and development.
In the Build phase, development teams can easily connect their SCM of choice – whether it’s Bitbucket, Gitlab, or Github – and continuous integration tools to gain visibility over their code. By enriching issues with context pulled from the toolchain, Jira Software enables developers to share status of code throughout its development lifecycle, align efforts to works in progress, and share development status with others. With less context-switching and team syncs, developers stay focused on building great software.
Before deploying, you need to conduct layers of testing in the Test phase. Tools such as Zephyr, Mabl, Mend (formerly WhiteSource), and Veracode allowing developers to get feedback on the quality of their code before it reaches users. By automatically attaching high severity findings and its remediation advice to issues, Jira Software guides developers to deliver quality code.
As features hit the Deploy phase, development teams can easily connect their continuous deployment of choice – whether it’s Jenkins, Octopus Deploy, and Bitbucket pipelines – and feature flag tools – such as LaunchDarkly and Split – to deliver features reliably and predictably. By enriching issues with context pulled from the toolchain, Jira Software helps teams share deployment status, monitor build releases, and coordinate a release plan. Now, software teams are aligned on releases with less context-switching and team syncs.
As features progress into the Operate phase, it’s paramount that all code – new and old – work harmoniously in production. Support the operation of all that code with clear communication protocols with on-call tools, like Pagerduty and Opsgenie, or incident management and communications tools, like Jira Service Management and Statuspage. Automatically link incidents to issues, view on-call rosters, and engage on-call assignees from issues directly to consistently meet SLAs.
Recover quickly when unexpected incidents occur in the Observe phase. Through Jira integrations with logging tools, like Datadog and Sumo Logic, or performance monitoring tools, like New Relic and Dynatrace, you can continuously and automatically keep Jira issues updated with the latest information on errors and incidents. Through Jira Software integrations, teams can identify and visualize error patterns for quick troubleshooting.
In the Continuous Feedback phase, the goal is to iterate on your features with feedback from users. Deliver value in future iterations by embedding customer conversation and support tickets to Jira issues, adding valuable context to work in the product backlog.

These are just eight examples to highlight the breadth of options available. For the full list of partner applications, visit here.

Also, don’t forget to check out the Lightning Talks: Apps for DevOps webinar to learn more about the apps we support. Visit here for details.

Questions?

If you have questions or need help, don’t hesitate to reach out. We’d love to hear from you. Here are just a few ways to get in touch:

Comment on the community post. It’s likely other users have similar questions, and we love receiving feedback directly from our customers.
Customers on a paid license are welcome to reach out to our support team via https://support.atlassian.com/contact/
For product feedback, use the “Give feedback” within the product - this feedback goes directly to our teams.