These are the major features that we’re currently working on. Use the buttons below to get an email when we’re ready to ship.

Last updated October 2020

Config as Code Config as Code Jira Service Desk Jira Service Desk

Config as Code

TL;DR - Config as Code for projects is a human-readable version of the application deployment or runbook process stored in git source control.

Teams will be able to turn on Git integration per project, and Octopus will store the process to the Git repository configured for the project. Users will also be able to view and edit the deployment process with the process editor in the Octopus Web Portal, and when saved, Octopus will create a commit with the changes to the Git repository.

Jira Service Desk

Change management can be a nightmare. Some development teams spend more time getting approvals than it takes them to code and test changes.

To help with this process, we're adding integrated change management with Jira Service Desk. This functionality will enable teams to automatically create change request tickets during their deployments. Further, Octopus will check change requests to ensure they have the appropriate approvals before proceeding with deployments. If there are outstanding approvals, Octopus will pause the deployment and automatically resume when approval has been granted.