Nowadays, software is becoming multi-component (for instance microservices-based) and also distributed between various geo-locations. Therefore, it is not enough just to put all the scope into a single Jira version and release as one piece of code.
After a number of consulting engagements, we see that reality is the following:
Each component has its own code repository, software development life cycle and as a result own release cycle
“Version” deserves its own life cycle. Released/Unreleased statuses are not covering extensive Release Management practices.
Individual components/services could be released to various environments (including development, staging, integration and production environments). Each environment can host different version of the same component at any moment of time.
In order to deliver particular business functionality, versions of multiple components has to be delivered to proper environments where the entire solution will be integrated.
Tracking is essential at package level in order to orchestrate delivery of entire solution. This assumes packaging of multiple versions of each component into single deliverable, define the workflow of it, provide necessary reporting to manage it.
As a result, the role of Release Manager is becoming more and more important in today's HiTech companies. In order to automate Release Manager’s daily routine, efficient tools are an absolute must. As Jira standard functionality is not cover the above-mentioned challenges, we decided to create the Release Management app for Jira Cloud.
Release Management Add-on is well suited for orchestrating release packages that include versions from multiple Jira projects. In essence, the add-on extends Jira version workflow, helps packaging multiple versions into releases, provides tools for tracking and managing as well as some extras.