Changes to the Toolchain page

[StannousBaratheon]

Atlassian introduced the toolchain page two years ago, a project administrator experience that made it possible to discover, connect, and visualize toolchains, all within Jira Software. Today we are announcing changes the toolchain experience to streamline discovery and make configuration more contextual.

Access the toolchain page under Projects > Project settings to begin exploring the DevOps possibilities for your teams. This page now focus on tool discovery, allowing administrators to find and connect integrations that extend Jira and customise the toolchain used by their teams.

These tools enable powerful features in Jira such as code, project pages, security, incidents, and more. Configuring these features is now done in context via the various feature pages providing a more streamlined experience for admins and users alike.

 

Code

It's no longer possible to manually link repositories to a project via the toolchain page. To link a repository, include issue keys in your branch names, commit messages, and pull requests. Please refer to the documentation for further information. 

Why was this removed?

Jira utilises development information like commits, pull requests, and branches to form associations between Jira issues and your code. These connections are required to power various development features in Jira which are not enabled by connecting a repository alone. Repositories are still implicitly linked through code references. This ensures correct configuration of data powered features and provides an accurate representation of what repositories are being used by the project.

Of course we are always looking for ways to further improve the experience. If you've got any feedback or thoughts on the above feel free to comment below.

[John Funk]

Thanks for the update!