Plutora Feature Release Notes For Early March 2021

New Features

Release Management KPIs Dashboard

Now, Release Management KPIs Dashboard allows enterprises to review key release metrics in order to identify positive or negative trends, and identify potential areas for improvement:
  • The new dashboard will be located under:
  • Users will be able to :
    • Review Release KPIs for up to a two-year period using the date range filters.
    • Filter the dashboard based on Portfolio Association, Release Type, and Release Status.
    • Answer the following questions by looking at their release KPIs:
      • Are the number of planned releases increasing?
      • Are the number of unplanned or emergency releases decreasing?
      • Is release duration decreasing and what phase of the release is taking the longest?
      • Are we increasing the number of delivered scope items?
      • How much of the delivered scope items are new features vs defect fixes?
      • How much of the delivered scope items are related to Compliance, Security, Performance, Technical Debt vs strategic goals and initiatives?
      • Are the number of Post Implementation Incidents decreasing?
      • How much of an impact to service availability has there been as a result of new releases to production?
    • Important: All data relating to Post Implementation Incidents is derived from the PIR module.

Builds Entity

Introducing the Builds entity, which provides visibility and tracking of build progression for every Continuous Integration and Continuous Delivery (CI/CD) Pipeline in your enterprise.
Combined with Plutora’s Release Management and Environment Management the Builds entity enables you to see:
  • What software versions are being delivered as part of a Release?
  • What versions are currently deployed in your non-production environments?
  • What user stories and defect fixes are included in each build?
Now, when the Builds entity has been enabled in Build Setup Customization:
  • Users can control who can create, edit, and delete Builds using the new user permissions under Systems Manager:
    • Create Builds.
    • Edit Builds.
    • Delete Builds.
    • Create/Delete Build Public Query Builder.
  • Users can create new Builds in Plutora using three different options:
    • Manual entry allows you to capture basic Builds information such as Build #, Build Tag, and Branch Name, for each System and link it to the relevant Release, Changes, and Environment:
      • Build Tag: The external version number, often in the semantic format of Major.Minor.Patch.
      • Build #: The CI-generated internal version number.
      • Branch Name: The name of the relevant Git branch.
    • Automated Builds can be created using the Jenkins Integration Adapter and they retrieve more detailed information from Jenkins for each Build, including the job details, the count and list of commits included, as well as a list of any artifacts created.
    • Automated Builds can also be created using Plutora’s API so users can push Build information from any CI application into Plutora:
      • For the full list of endpoints see Add Builds Via APIs:
        • GET /Builds
        • POST /Builds
        • DELETE /Builds/{id}
        • GET /Builds/{id}
        • PUT /Builds/{id}
        • POST /Builds/{id}/JobExecutions
        • GET /Builds/{id}/Changes
        • PUT /Builds/{id}/Changes
  • Users will be able to view what Build is deployed to each Environment in the Environment Manager and Continuous Delivery Pipeline dashboard. The Build information displayed will be as follows:
    • Tag | Build Number (Branch Name) or just Build Number (Branch Name) if there is no tag.
  • Users will be able to govern the process of deploying Builds across the Continuous Delivery Pipeline and have greater visibility of Build progression using TECRs and Deployment Plan Activities.
  • Users will also be able to trigger deployments and initiate automated testing from TECRs and Deployment Plan Activities using the Jenkins Integration Adapter.
  • Users will be able to update the Build information for an Environment via the APIs so they can push this information to Plutora from any Deployment application as a step in the process.

Release Calendar Filters


Blockout Period Grid


  • Blockout Period page is a flat grid, instead of a tree structure, which improves performance and loading times, and makes it more consistent with other data grids.

Delete Confirmation Prompts


Deployment Plan Email Notification Triggers


  • Email Template Wizard’s Deployment Plan Activity entity can provide more comprehensive and regular updates for Deployment Plans with the following new triggers:
    • Activity status updated.
    • New comment added.
    • Planned dates modified.
    • Any value updated.
  • The triggers Any value updated and Planned dates modified have Approved Mode and Execution Mode toggle switches, so users can set the mode when notifications are sent.

Version Number


Regional Release Schedule

Type Schedule*
User Acceptance Testing March 4, 2021
Asia-Pacific Release March 10, 2021
8:00 pm – 11:00 pm
Europe Release March 14, 2021
11:00 pm – 2:00 am
Americas Release March 14, 2021
8:00 pm – 11:00 pm

*Subject to change.

Back to the top arrow

Related Articles


Be the first to find out about new features. Subscribe to the Release Notes email.

Was this article helpful?

Thanks for your answer!