Releases Approval Dashboard

This extension allows you to easily view releases that are pending approval for your user, allowing you to approve them directly from a simple grid view. You can approve them one by one or in batch.

Requirements

Starting with version 2.0.0, this extension uses Azure DevOps REST API version 7.2. It works with Azure DevOps Services and with Azure DevOps Server versions that support REST API 7.2. Older on-premises servers (Azure DevOps Server 2022 and earlier, TFS) are no longer supported. On those servers, use version 1.x of the extension.

Getting started

1. From the Pipeline hub, select the Approve Release option

2. The grid will display all releases pending approval

3. From each release, you can approve or reject Note: If you prefer, you can select more than one release for approval (or rejection) and select Approve All (Reject All) button.

4. If you want/need, You can schedule deployment for later with deferred deployment feature:

   

   Important!!!

   The date picker field in deferred deployment section has a know issue. The component doesn´t appear with selected Azure DevOps theme. This occurs because this component is from Office UI library and I don´t know how to apply Azure DevOps themes to this library yet. This is a backlog item for next releases.

Feature Backlog

This release has minimal functionality to perform approvals, but we are working on more features and enhancements to refine and complete the extension.

Here are some features we're working on. Feel free to suggest any other feature.

• Grid filters: allows to filter pending approvals by definition, identifier, status or stage/environment.
• Sortable columns: allows to sort items.
• UI improvements:
  • add theme support for deferred deployment date picker.
  • add stage grouping (Issue #30)

Pipeline

Contributors

Special thanks to Vinicius Moura (Microsoft MVP) for always helping with Azure DevOps related questions and ideas.

Contribute

This extension is free, but if you enjoyed the work and would like to help the developer stay up: