1. Home
  2. Knowledge Base
  3. Release Notes
  4. Plutora Feature Release Notes Late June 2020

Plutora Feature Release Notes Late June 2020

Features Included in the Late June 2020 Release

Version Number
2.8.0

Regional Release Schedule

Type Schedule*
User Acceptance Testing June 23, 2020
Asia-Pacific Release July 2, 2020
7:30 pm – 10:30 pm AEST
Europe Release July 6, 2020
1:00 am – 4:00 am BST
Americas Release July 5, 2020
9:00 pm – 12:00 am PDT

*Subject to change.

Please note: During this release window, due to the Redis cache being rebuilt, a 45-minute outage is expected for US and Asia-Pacific customers, and a 20-minute outage for UK customers.

Functionality Enhancements

Use Plutora Analytics to locate environment drift.

“As an Environment Manager, I want to find Environments that are not the correct version, so I can update them.”

Environment Drift Dashboard

  • Now, the Environment Drift Report allows users to track version numbers across the Environments of selected Environment Groups.
The members of User Groups can now approve or reject Environment Bookings.

“As an Environment Manager, I want to select a User Group as an Environment Booking Approver, so that any user in the group can approve or reject those Environment Bookings.”

User Groups can Approve Environment Bookings

Bulk approve Environment Bookings in Releases and TEBRs.

“As a Release Manager, I want to approve or reject multiple Environment Bookings at once, so that I save time.”

Bulk Approve Environment Bookings

  • Previously, Environment Bookings in Releases and TEBRs had to be approved one by one.
  • Now, users can save time by bulk approving Environment Bookings in Enterprise, Project, and Independent Releases, and TEBRs (with or without a Release).
    • Select the checkboxes of Environments individually, or click the Select All checkbox to select all the Environments in all active Phases.
Delete Initiative Management Form Instances via the API, and receive combo box entity data via the API in an automatically paginated form.

“As a Release Manager, I want to use the API to delete Form Instances, so that they are automatically deleted via an integration layer.”

Initiative Management API Enhancements

  • Now, the users of Plutora’s API can:
    • Delete Initiative Management Form Instances using the following call:
      • DELETE /formInstance/Delete/{id}
    • Receive automatically paginated Release, System, Environment, User, and Team entity data using the following call:
      • GET /formInstance/{formInstanceId}/ComboBoxElementFilter/{elementId}
        • Maximum of 100 records per page.
Enhancements for Releases Systems API.

“As a Release Manager, I want to use the API to manage my Impacted and Regression Systems for Releases, so that they are automatically updated via an integration layer.”

Release System Dependencies

  • Now, the users of Plutora’s API can:
    • View the Downstream Dependency Systems of Releases using the following call:
      • GET /releases/{id}/systems
        • If isGhost is True, the System is a Downstream Dependency.
    • Link and unlink Systems to Releases in bulk using the following calls:
      • POST /releases/systems
      • DELETE /releases/systems
Multiple enhancements for the Systems tab user interface of Project and Independent Releases.

As a Release Manager, I want to add an Impacted System to a Project or Independent Release and automatically see all the associated Downstream Systems as Regression Systems, so that I am informed of regression risks.

Release Systems Enhancements

  • Now, when adding or editing a Project or Independent Release:
    • Dragging and dropping a System which has Downstream Dependencies into the Impacted System or Regression System panels will automatically add those dependencies to the Regression Systems panel as grayed-out and not clickable records marked (downstream dependency).
    • Deleted Systems will appear as grayed-out and not clickable records marked (deleted). Deleted System dependencies will not be shown.
    • Logic has been added to prevent the creation of circular dependencies.
    • System linking and unlinking is tracked in Audit History.
Enhancements for Systems Dependencies API.

“As an Environment Manager, I want to use the API to manage Systems Dependencies, so that they are automatically updated via an integration layer.”

Systems Dependencies

  • Now, the users of Plutora’s API can manage Systems Dependencies using the following calls:
    • GET systems/{id}/systemDependencies
    • POST systems/{id}/systemDependencies/upstream
    • POST systems/{id}/systemDependencies/downstream
    • DELETE systems/{id}/systemDependencies/{deleteSystemId}
  • Logic has been added to prevent the creation of circular dependencies.
Plutora’s Swagger is now better organized and more consistent.

“As a user of Swagger, I want drop-down menus to have their items listed alphabetically, so I can find the item I am looking for more quickly.”

Swagger Enhancements

  • Now, Swagger’s menus are in alphabetical order and the entity name IMFormInstance is used consistently.

Resolved Support Issues

Plutora

  • 16865: [API] The Release Activities of Project and Independent Releases are no longer given a Release Framework.
  • 16970: [Release Schedule and Environment Schedule] Copied filters now load when a logged-out user pastes the filter URL into a browser and logs in.
  • 17136, 17725: [Release Activities] Enterprise Release Activities created from a template with the Release Framework Child, now have the correct status: N/A.
  • 17173, 17016, 17152: [API, Changes, and Jira Customization] Changes created via the Jira integration and the external API are now recorded in the StatusTrack tables.
  • 17275: [Release Manager] Audit History now shows Release Activity Actual Completed Date in the user's time instead of UTC.
  • 17297: [API] Aliases of deleted Systems can now be used in calls to POST /systems.
  • 17377: [Release Manager and Comments Customization] rn characters no longer appear in emails.
  • 17497: [Release Manager] Stakeholders can now be updated to a different user or User Group, and the first Accountable Stakeholder added to a Release now becomes that Release's Owner. 
  • 17550, 17750, 17759: [Deployment Plan and Systems Manager] Session timeout prompts now appear instead of a 500 error.
  • 17568: [Initiative Management and Email Template Wizard] For Initiative Management Form entities and trigger Status Updated, the entity field [[Update_via_Secure_URL]] now works as expected.
  • 17613: [Release Calendar] Clicking + more now displays records with the correct time zone adjustment.
  • 17746: [Initiative Management and Email Template Wizard] Initiative Management Form entities and trigger New Comment now sends emails to Recipients.
  • 17792, 17858: [Common] Query Builder public queries now work as expected.
  • 17834: [Deployment Plan] Column width in Timeline view now remains the same after a user opens and closes an Activity.

 

Back to the top arrow

Be the first to find out about new features. Subscribe to the Release Notes email. Subscribe Now
Updated on July 1, 2020

Related Articles