Features Included in Red Fox
Regional Release Schedule
Major Functionality Enhancements
Blockout Period Types
- Users can choose to select Blockout Period Types under Customizations.
- The option to add icons are provided via a drop-down.
- The Blockout Period Types will be displayed in the following places:
Capacity Management Further Enhancement
- Users can view the overall Capacity Management ability of an Enterprise Release.
- One overall bucket will be displayed on the first grid of the Enterprise Release > Capacity Tab.
- The percentage of consumption of each Capacity Item compared to the overall Capacity size will be displayed on this big Bucket.
- A Watermark functionality has been added.
- With this Watermark functionality, users can show the Planned and Actual Capacity Size within the same Bucket.
- For example, if this functionality is turned on, the Planned Capacity will be displayed as a lighter color and Actual will be displayed as darker color in the Capacity Bucket.
- A red or green arrow will be displayed to present how many capacity items are above/below the Threshold.
- Users can set the Total Viability Marker for the total bucket.
- Performance of loading Capacity tab has also been improved.
Deployment Plan Bulk Update
- The functionality to bulk update stakeholders has been added to the Deployment Plan.
- By multi-selecting several Deployment Plans and clicking the ‘Bulk update‘ button under the “Action” button, users can add multiple Stakeholders to those Deployment Plans with a few clicks.
Uploading Deployment Tasks Group
- Added a new column in the XLS template called “Group Tasks”.
- This column is not mandatory as Deployment Tasks do not have to belong to a specific group.
- The name that is entered in this column will be the name of the group task. Any deployment tasks that match the Deployment Plan Group name, will be grouped together.
Functional Enhancements in Red Fox Release 3.0.108
Bulk Deletion of Deployment Plans
- Users can delete several Deployment Plans by multi-selecting several Deployment Plans and clicking the Delete button located on the top right corner of the Deployment Plan grid.
- This action can be performed only if the users have the correct permission.
Test Environment Booking Request with Systems
- Users can now add Systems to a Test Environment Booking Request.
- This field is multi-selectable and users will be able to Live Search the System.
User Groups for Test Environment Change/Booking Request
- User Groups have been added to the Query Builder and Bulk Updates.
- Members of the User Group will receive email notifications depending on which notifications have been enabled.
Test Environment Change Request Grid with Additional Information
- Users now have the ability to Display Additional Information on the Test Environment Change Request Grid.
- By clicking the Action > Grid Column Selector, a pop up window will open and users will have the ability to select which custom fields will be displayed on the Test Environment Change Request Grid via this list.
Test Environment Booking Request Grid with Additional Information
- Users now have the ability to Display Additional Information on the Test Environment Booking Request Grid.
- By clicking the Action > Grid Column Selector, a popup window will be brought up and users will have the ability to select which custom fields will be displayed on the Test Environment Booking Request Grid via this list.
My Environment Bookings – Bulk Update
- Users can bulk update several Test Environment Bookings Status at one time.
- By multi-selecting the checkbox of the first column of My Environment Bookings Grid, users can click the Bulk Update button under Action button to carry out this new functionality.
“Phase Usage” for Environment Groups
- Users can now add “Phase Usage” for the Environment Groups.
- The “Phase Usage” can be set under the Environment Group window > “Used for Phase” option.
- This field has also been added to the Environment Groups Management window with an extra column called “Used for Phase” for each Environment Group record.
Approving Intelligence for Environment Allocation
- Environment Allocations that have been approved will be marked with a green line instead of a red line in the Environment Schedule – Conflict View.
Environment Utilization Enhancement
- A ‘View By Date’ button has been added to the Environments Grid.
- The user can specify a date range for Environments to show whether or not the Environment is utilized.
Environment Group Management Window Improvements
- A ‘Detail’ button has been added to the Environment Groups list grid.
- Users can click this button to open a specific Environment Group.
Test Environment Booking Requests – Environment is Not Mandatory
- When creating a new Test Environment Booking Request, the “Environment or Environment Group” field will not be mandatory.
- The Environment or Environment Group can be added at a later time which will allocate the Environment.
‘Actual Completed On’ Date Field for an Activity can be Used To Determine the Traffic Lights
- Under Settings > Customization > Releases > Enterprise Release Setup, a new setting called ‘Calculate Release Traffic Lights’ has been added.
- The Traffic Lights will also be based on the ‘Actual Completed On’ date instead of the Completed Date.
- This option will be applied to both Release Phases and Gates.
Changes Grid with Additional Information
- Users now have the ability to Display Additional Information on the Changes Grid.
- By clicking the Action drop-down menu > Select Columns, a pop up window will be brought up and users will have the ability to select which custom fields will be displayed on the Changes Grid via this list.
- Changes – Delivery Release Tab Updates
- The Releases that appear in the Delivery Release tab will no longer depend on the Portfolio Association of both Changes and Release.
- For the Release to appear, both Changes and Release must have the same system impacting them and have a Release Implementation date greater than today.
Duplicating a Change
- Users will have the ability to duplicate a Change via the Changes Grid.
- A checkbox column has been added to the grid so users can click the Duplicate Change button under the Action button to duplicate the corresponding Change.
Releases Criteria/Activity Permissions Redesign
- Previous permissions of Create Activities/ Create Criteria have been merged into one Permission called “Create Activity”.
- Previous permissions of Update Activities/ Create Criteria have been merged into one Permission called “Update Activity”.
- Previous permissions of Delete Activities/ Create Criteria have been merged into one Permission called “Delete Activity”.
- These permissions have been placed in a separate category of Permissions called “Release Activities”.
- Roles that have one permission or the other will automatically have this merged Permission. Roles that do not, will continue to have this permission unchecked.
Permission to Update Release Framework
- A new Permission called “Update Activity Release Framework” has been added to the Release Activities section.
- This allows the user to restrict access to change the Release Framework of the Activity/Criteria.
Permission to Update Activity Due Dates
- A new Permission called “Update Activity Due Date” has been added to the Release Activities section.
- This allows the user to restrict access to change and update Activity/Criteria Due Dates.
Release Calendar Report
- A new report called “Release Calendar” has been added to the Reports Center under All Reports > Releases.
- Upon selecting the Date Range and Releases Type, all the corresponding Releases will be displayed under a Calendar view.
Additional Information Usability Enhancement
- When accessing the Additional Information tab, the last visited tab will be opened.
Blockout Period Attachments
- Users can now add Attachments for Blockouts by clicking the clip icon in the Blockout Window.
User Management & Groups
- The usability of ‘Manage Permissions‘ and ‘User Groups‘ have been improved.
- When the user clicks the ‘Add Role’ or ‘Add User Group’ button, the Name field will be editable immediately for input.
- The user can use the ‘Tab’ button to move to the next editable field.
Last Page Visited
- When the user logs into Plutora, the last page that was visited will be loaded instead of loading the Dashboard automatically.
|In some instances, Phase or Gate names are not appearing immediately after changing the release dependency.||Phase/Gate names will be brought up immediately after changing the release dependency.|
|If the user creates a new non-Enterprise Release and upon saving, navigates to the Systems tab, the available systems would sometimes not appear.||The Systems available will be listed when users create a new non-Enterprise Release.|
|Email notifications have been sent out for some Release Activities several days later even though the Release Activities status have been marked as completed.||All Release Activities that have a status of completed will no longer send out email notifications.|
|Release Types that have been deleted from customizations still appear in the Release Calendar filters.||Those Release Types that have been deleted no longer appear as a filter.|
|When deleting a Phase or Gate from a non-Enterprise Release, the row was not removed immediately. However, after re-opening the Release the Phase or Gate is still removed.||The Phase or Gate when deleted will be removed immediately.|
|Under the Environment Window, the System field would sometimes no longer expand once it has been collapsed.||The Systems drop down correctly expands and collapses.|
|The ‘From Today’ condition in the Query Builder would sometimes require the user to fill in the field even though this field is automatically grayed out.||Users can filter the Test Environment Change Request Grid Query Builder with the ‘from today’ option as per usual.|
|In Internet Explorer 10/11, when there are several Environment Layer Cards in the Test Environment Change Request, the last layer card would not display correctly.||The last Environment Layer card now correctly displays in the Test Environment Change Request window.|
|In Internet Explorer 11, the Environment Schedule tooltip would not appear correctly if the information exceeded a certain text limit.||The tool tip now correctly displays the Environment Schedule information.|
|The use of ‘less than'(<) or ‘greater than'(>) signs in customizations would reflect the HTML entity symbol instead of the given character. i.e. < and > was shown instead of ‘<‘ and ‘>’ respectively.||The HTML Entity will be displayed as < and > when specified.|
|For Releases, Systems and Environments, the unique Name check would sometimes offer an already used value.||Plutora will now always offer a unique value to the user.|
|If an Organization Structure has been applied to a Release that has since been deleted, the user will no longer be able to remove the organization structure.||The user can now successfully delete and re-assign the Organization Structure for those that have an association to a Release.|
|If a User Group was associated to a Test Environment Change Request or Test Environment Booking Request, the user was not able to remove the corresponding User Group.||User Groups are now Soft Deleted so the data is retained.|