Workforce Rostering - Release 4.08.00
We have been enhancing WORKSuite and MyTime since the last release, adding new features and addressing known bugs. This overview outlines the updates available from week commencing 15th September 2025.
To ensure the best experience with this update, we recommend clearing your browser's cookies and cache. This helps prevent loading issues and ensures new features display correctly.
Below are the features and bug fixes included in this release:
Any features which require additional explanation or steps to be performed, are detailed, separately on their own pages and are linked against the relevant features in the tables below.
New Functionality and Improvements
|
JIRA Ref |
Description |
|---|---|
|
WTSSUP-122 |
Updated the PLAN section to allow the removal of old unused teams. Previously if a team previously had shifts published against it, then deletion of that team was prevented. This has now been updated to allow the removal from the PLAN section if the published dates are in the past. Teams that have had shift published in the past will still remain in the Manage page, but will have a “Retired” Prefix. Teams that have shifts in the future cannot be deleted. |
|
WS-10099 |
Updated our application to the latest stable Angular version to enhance performance and security. Angular is a robust, open-source web application framework that we use to develop the WorkSuite application. We aim to update this framework every 6 months and users may experience minor visual changes when this occurs. |
Bug Fixes
|
JIRA Ref |
Description |
|---|---|
|
WTSSUP-262 |
Resolved an issue with clocking exceptions where a night shift was creating an additional unknown event on the day following the night shift. |
|
WS-10672 |
Resolved an issue with the day view that affected holidays on a night shift. When a full day’s holiday was applied to a night shift, the following night shift would not display on the day view. |
|
WTSSUP-258 |
Resolved an issue with missing data entry that was causing the Working Time Regulations report to not run. Better handling of this error means that the Report will still run in this scenario. |
|
WS-10746 / WS-10727 |
Resolved an issue with duplicate Clocking events. Duplicate and repeated events will be ignored (as per system settings) and the system will only allow 1 clock in and 1 clock out per shift. |
|
WS-10744 |
Resolved an issue with miscellaneous variances not being included in a full day absence in the variance report. For example if a 12 hours shift had a 2 hour miscellaneous variance on it, then the absence was reported as 10 hours instead of 12. |
|
WS-10411 |
Resolved an issue with the calendar report which was missing the month names in the appropriate places. |
|
WS-10724 |
Resolved an issue with the My Holidays screen in MyTime that prevented users from scrolling to the next year. |
|
WS-10774 |
Resolved an issue with accounts that track number of shifts (using the “is shift account” functionality). When adding a shift change, this wasn’t changing the number of shifts counted by the account. |
UAT Fixes
This section is used to capture any fixes that are fixed between deploying to customer UAT environments and Live deployments. The following tickets were created since the first UAT deployment and have been fixed before releasing into the next live release.
|
JIRA Ref |
Description |
|---|---|
|
WS-10818 |
UAT issue only (not reproducible in live) Resolved an issue with variances not displaying any information in the Manage page. All variances were displaying a blank cell. |
|
WS-10855 |
UAT issue only (not reproducible in live) Resolved an issue with the new functionality that allows administrators to delete teams in PLAN. This was removing teams completely from the manage page instead of saving historical records. |