This glossary lists and defines all the terms and acronyms you are likely to see in Plutora and Plutora Test.

# | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z



An Activity is a defined action with an output. Activities are assigned against a Phase or Gate within a Project and are assigned to individuals with due dates and measureable KPIs.

Additional Information Field.

A custom field created by the user in the Release Manager which allows additional information to be added.


See System.

An executable file that allows Plutora Test to peform automated testing. AutoHub executes test files, listens for the responses, and puts those responses into Plutora Test. See Plutora Test Selenium Integration for more information.


Blockout Periods such as End of Quarter activities or holidays are added Plutora to show when a Release cannot occur. Blockout periods have associated organizational levels and appear in the Release Schedule.
Blockout Periods are also called Blackout Periods.


Customer Acceptance Testing.

A Change is a request to deliver new functionality or to make updates to existing functionality within a Project. A Change lists the technical aspects of a functional change to a System and includes impacts, timings, approvals, and stakeholders.

The status of a Change, for example, On Hold, Pending Approval, or Approved. Changes are assigned a Change Status in the Change Manager page. The Change Statuses themselves are added, sorted, edited, deleted in Change Status Customization.

The theme of a Change, for example, Competitiveness, Investment or Legislative. Changes are assigned Change Themes in the Change Manager page. The Change Themes themselves are added, sorted, edited or deleted in Change Theme Customization.

The type of Change, for example, Feature, Enhancement or Change Request. Changes are assigned Change Types in the Change Manager page. The Change Types themselves are added, sorted, edited or deleted in Change Type Customization.

An independent or other kind of release that belongs to a parent release.

A Criteria is an exit or entry decision point (for instance, endorsed status). Criteria are assigned against a gate within a project and are assigned to individuals with due dates and measurable KPIs.


After logging in, the first page users will see is the Dashboard. This read-only page shows a snapshot of change pipeline, releases, systems, environments and their usage.

Deployment is the physical act of delivering new or updated functionality into an environment, system or platform.

Deployment plans track key stages associated with the deployment activity. Deployment plans include details regarding systems, release ID, stakeholders, and timelines associated with the change.


Environment Change Request.

Environments Impact Matrix.

The title of the Environment Schedule page.

An Enterprise Release is the coordinated delivery of multiple projects to deliver new functionality into a production Environment. An Enterprise Release is made up of several child Projects.

An Entity is functional area of Plutora. Each Entity has associated Triggers.

Entity Fields are codes representing information, for example, the company name. The Email Template Wizard Pop Up has a range of Entity Fields available in the Email Template tab, allowing users to set up automatic emails and populate them with information.

An Environment is a System that has been associated to an Environment Group. Several instances of a System are used during various Phases of testing (ie UAT, SIT, CAT, STRESS).

An Environment Group is cluster of Systems that combine together to support with a particular phase within a delivery lifecycle. Environment Groups are generally used for test phases of a release and replicate the production environment.

The triangles that appear on the Environment Schedule under the Environment Groups View.

An Environment Request is:

  • TECR – An application to change part or all of an environment, such as its IP address.
  • TEBR – An application to book an environment for a certain amount of time.





A Gate is a milestone point in time where a criteria or approval needs to be met for the project or release to remain on schedule.

The Grid Column Selector allows users to filter the content of their pages. It is found in the headings above the columns of data, and contains search fields and drop-down menus that allow users to filter each column’s data. The Grid Column Selector of the Release Manager page appears below.
Releas Manager Grid Column Selector
Users can also add columns containing their own custom data (added using one of the Custom Field Customizations) by selecting Grid Column Selector from the Action drop-down menu.





Key Performance Indicator.


Plutora’s Live Search fields perform an incremental search on text as it is typed into the field, speeding up the search process and providing immediate feedback.


My Environment Bookings are the Environment Bookings made by dragging Environments to the right side of the Environments tab of the Enterprise, Project and Independent Release pop ups. The title “My Environment Bookings” can be customized using the Title Names Customization.



Organizations usually contain a number of departments, branches, workgroups or individuals. These are represented as the organization structure.

An outage is a period of time when a service is not available.


A release containing one or more child releases.

Permissions are the settings that dictate what parts of Plutora are visible to each user role. See Manage Permissions to update user permissions or Permissions for the full list of permissions.

A Phase is a period of time within a Project or Release where activities need to be completed (for instance, design, development, testing, deployment, etc). Can also be called a Sprint.

Post-Implementation Review.

The expanding and contracting dots that appear near the top of the screen while Plutora is loading a page or pop up.

Plutora’s test management software. Previously called Stryka.

A Portfolio Association is a single level of an Organization Structure.

Another name for Change Manager.

A Project is an initiative undertaken to deliver new functionality or updates to existing functionality. A Project is made up of several Phases and Gates that form part of the delivery lifecycle. Projects are deployed independently or as part of an enterprise release package.


The pop up that appears after clicking the Query Builder button. The Query Builder allows users to add, edit and save public and private search queries.


Red, Amber, Green. These colors refer to the Traffic Lights in Release Manager’s Status column. See Settings for more information.

Root Cause Analysis.

The red top left corner of a field, which appears when a field contains unsaved information.
Red Hat.

A release is a product, such as a software version, that is made available to the public.
The Releases function allows users to add, edit and delete upcoming Releases, manage stage gates and approvals. All Releases are visible via the Release Schedule.

A Release Package is a group of Releases within a user-defined date range, which can be reported on as a group. Also known as a Release Window.

The Release Pipeline is the Environments from development to production that are involved in building, testing, and releasing software.

The Release Type can be defined by the user. The default Plutora release types are Enterprise Release or Independent Project.

Execute standard reports to provide detailed metrics and outputs across Releases, Changes, Environments and Deployments. Custom Reporting can be requested by contacting Plutora Support.


Selenium provides a record/playback tool for authoring tests without the need to learn a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including C#, Groovy, Java, Perl, PHP, Python, Ruby, JavaScript, and Scala. See Plutora Test Selenium Integration.

Secure File Transfer Protocol. A network protocol that allows file access, file transfer, and file management over the Internet.

System Impact Matrix.

System Integration Testing.

See Phase.

Single Sign On.

Stakeholders are defined as an owner or impacted party to an Environment, Release, activity, criteria, Deployment Plan, Change Request or any other feature of Plutora.

Stress Testing is testing beyond normal operational capacity, often to a breaking point, in order to observe the results.

The previous name for Plutora Test.

A System, or an Application, is a program designed to permit users to perform a group of coordinated functions, tasks or activities.

The System Impact Matrix shows users the impact a release will have on all systems and whether there is a progressive change or regression testing impact. This view allows user to understand the release dependencies relatively to other releases and systems.


Test Environment Change Request. Users can change this title in the Title Names customization.

The status of a TECR, for example, In Progress, Approved or Completed. Statuses are assigned in the Add a New TECR Pop Up or the Edit ECR Pop Up. Users can add, sort, edit or delete TECR Statuses in the TECR Status Customization.

Test Environment Booking Request. Users can change this title in the Title Names customization.

The titles of the tabs and buttons in Environment Manager and Environment Requests and elsewhere in Plutora. The default names are TECR, TEBR and My Environment Requests, but they can be customized to suit company requirements in the Title Names section of the Customization page.

Tool tips are small pop ups containing information. They appear after clicking tooltip items, for example, a scheduled environment in the Environment Schedule page, or a tooltip button.
Tooltip Button

Traffic Lights are:

  • Release Manager: The red, green, green outlined with red, and gray circles in the Status column, which show the Activity completion status for Phases and/or Gates. See Learn More About Traffic Lights.
  • View/Edit Release pop up: Under the Systems tab, the Deployment Status of Systems are shown by circles with the following meanings:
    • Green: Completed.
    • Amber: Pending.
    • Red: Rejected.

Triggers are events in Plutora, such as release updates. Triggers are associated with entities.


User Acceptance Testing.



A small application on the Dashboard that shows graphs and other reports. Widgets are updated from the Dashboard Administration page.





# | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z
Back to the top arrow

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

Was this article helpful?

1 found this helpful.