Plutora Release Notes for January 2023

New Features

Systems and Sub-systems

Navigation: Environment> Systems

Now, you can capture the details of applications along with the underlying microservices/components using Plutora Systems and Sub-systems

With this new feature, you can

  • Capture the details of your applications using Systems
  • Capture the details of the microservices/components that make up each of the Applications using Sub-systems
  • Capture the stakeholders responsible for each individual System and Sub-system
  • Capture the upstream and downstream dependencies from System to System or Sub-system to Sub-system so they are automatically highlighted as regression risks for each impacting Change and/or Release
  • Capture the full history and details of software builds for each System and Sub-system
  • Configure Automated Jobs in Plutora to orchestrate the CI/CD pipelines and test automation for each System and Sub-system

For more information, see Add or Edit Systems.

Sub-system Instances

Navigation: Environment> Manager

Now, its easier to accurately model each instance of your Applications along with each instance of the underlying Microservices using Plutora Environments and Sub-system instances.

With this new feature, you can

  • Model each instance of your Applications using Environments
  • Model each instance of your Microservices using Sub-system instances within an Environment
  • Capture the details of one or many software versions running on each Sub-system instance using Builds

This feature significantly reduces the number of Environments required to capture the instances of each microservice in non production along with the software version running on each instance, thus making it easier to perform Environment Booking Management and Release Management for Microservices

For more information, see Add or Edit Environments.

Set Target Builds

Navigation: Environment> Requests; Deployment> Manager

Now, you can request and approve the deployment of software builds for multiple Microservices within an Application using the Set Target Build configuration on a single Plutora TECR or Deployment Plan Activity. Upon completion of the Environment request within a TECR or Deployment Plan Activity the target build configuration will be applied to the Environment and all updates record to the deployment history

This enhancement enables users to clearly document the target Build configuration for an Environment used for AB Testing or Blue/Green and Canary deployments. It also provides better support technologies like Kubernetes where the deployment of a single manifest file can include new software versions for multiple microservices within an Application.For more information, see Add or Edit a TECR and Manage Deployment Plan Activities

Bug Fixes

  • 19256: [Customization] 'Delete and Replace' for custom field list items is not working
  • 27446: [Environment Health Check Dashboard] Page loads and displays white screen
  • 17787: [Environment Schedule] Reporting/GetLastUserFilter call can be slow when user's date range is large
  • 21886: [TEBR] System subtype within TEBR forms do not match with what is displayed within System subtype customisation menu
  • 24984: [System] ReSaving Automated Job will cause Save and Close button to grey out
  • 20609: Remove the ability to change Environments or Environment groups in Bookings modal
  • 26877: [Blockout][Release] Adding Blockouts reverts back to the current year after saving and closing
  • 27071, 27072: [Releases] Environments tab - Freezes after viewing several Environment Bookings
  • 26837: [Activities Kanban] Deleted Release still shows up in Kanban
  • 27168: [TEBR] Env/Env group booking alert will not display when creating/saving a TEBR
  • 27548, 27516: [Environment Schedule] Unable to filter by release when viewing by release
  • 27678: [Deployment Plan Activities] Automated Job is not using the correct password from integration hub parameters
  • 22104: [Changes/Performance] Changes module will not load if filter not applied
  • 26507: [Release] Navigating from Release Linked Items has different UX than direct navigation
  • 27010: DP Activity 'Editing' icon does not go away till editor closes the DP window
  • 24366, 24639: [Bulk Update Changes] Status field label and tooltip should be available when Workflow is enabled 2
  • 27578, 27654: [Deployment Plan] - Exporting to XLSX - Dependency does not properly display
  • 27617: [Deployment Plan] - Update Activity Status role no longer works independently and requires another permission to function
  • 27424: [System Impact Matrix] Query builder will not load
  • 27681: [Deployment Plan/TEBR] Saved query breaks the page
  • 27787: [Deployment Plan] List Select Custom Field cannot be cleared
  • 25473: [System] Export to XLS is not working consistently
  • 25645: [Email Template] Unable to update TEBR Status from 'Update via Secure URL' when workflow is enabled
  • 27300: [Integration Hub] Predefined GUID values are unexpectedly stripped of hyphens
  • 27726: [Release] When searching for environments to book, no environments associated to the release systems show up
  • 25541: [Release] Creating an Event manually is not possible if one is first created through the API
  • 26284, 26839: [Permissions] Cannot Delete or Add new DP Activities with DP Permissions set to My Portfolio
  • Release Drop down on TEBR & TECR timeout when a large number of open releases exist

Version Number


Regional Release Schedule

Type Schedule*
User Acceptance Testing November 17, 2022
Asia-Pacific Release January 16, 2023 7:30pm - 10:00pm (AEST)
Europe Release January 19, 2023 02:00am - 4:30am (BST)
Americas Release February 01, 2023 7:30pm - 10:00pm (PDT)

*Subject to change.

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!