Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Why do you need Release Management app?

Nowadays, the software is getting to be multicomponent becoming multi-component (for instance microservices-based) and also distributed between various geolocations. It 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 projectsengagements, we see that the reality is the following:

  • Each component has its own code repository, software development life cycle , and as a result own release cycle

  • Version “Version” deserves its own life cycle. Released/Unreleased statuses will not cover all the needsare not covering extensive Release Management practices.

  • The Individual components/services could be independently released to various environments (including development, staging, integration and production environments). Each environment can have a host different version of the same component at any moment of time.

  • In order to deliver particular business functionality, version versions of multiple components has to be delivered to propper proper environments and where the entire solution will be integrated.

  • Solution level of tracking is a mandatory Tracking is essential at package level in order to orchestrate delivery and integration of the entire solution. It will cover This assumes packaging of multiple versions of each component into one entitysingle deliverable, define the workflow of the entityit, provide necessary reporting on to manage it.

As a result, the role of Release manager Manager is getting to be becoming more and more important in modern today's HiTech companies. In order to automate Release manager’s workManager’s daily routine, efficient tools are needed as embedded functionality will an absolute must. As Jira standard functionality is not cover the above-mentioned challenges. This is why we have created , we decided to create the Release Management app for Jira Cloud.


Do you use Jira server Server or data centreDataCenter? Please find Release Management for Jira Server/ Data Centertake a look at Server / DataCenter versions of our Add-on.

Typical use cases

Release management Management Add-on is well suited for orchestrating complex releases which include version release packages that include versions from multiple Jira projects. Release management extends version workflow and helps to better visualize version or release life cycleThe typical use case is 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.

The original use case is defined in the following article: - Release Management of microservices-based solution.

Key Features

Available now:

  • Organize cross-project releases on a single Release Board.

  • Design custom Version Workflow and visualize it in a handy way.workflow and map it to standard Released/Unreleased statuses.

  • Visualize the flow on Kanban style board to manage it.

  • Public REST API with built-in OpenAPI documentation as extension.

Coming soon:

  • Share release boards with individual users and groups or whole project team.

  • Grant releases board administration permission to users and groups.

  • Public REST API with built-in OpenAPI documentation.

QuickstartQuick start: Create your first release board

Release management “Release Management” menu item will appear in the main menu, after Release management Management app is installed.


Also, release management Release Management app is accessible from the project menuemenu:



    1. Select "Release Management" to view all available Release Boards or/and


    1. create a new one.


    2. Click "Create board" button; specify the new board name, projects from which to import versions, and then click confirm by clicking "Create board" buttonitem. 


    3. Once the board is created, you are will be automatically redirected to its Version Board Versions tab.

    • Versions tab has three


    • “default“ columns, namely Todo, In Progress, Done

    • a simple workflow which can be customized (TODO) by a board administrator in the board settingsIf you are an administrator of the board you can clicking on settings to customize version workflow to your needs.

    • By default,


    • all Unreleased versions are placed into default “Unreleased” column (Todo) and respectively all Released versions are placed to default “Released” column (Done)


    Please navigate to the next sections to find out more features and services.