Workforce Rostering - Release 4.07.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 |
|---|---|
|
WS-10658 |
Updated the TIME section to better handle unknown events. Previously if a clocking event fell outside of the threshold set in the system (e.g. threshold set to 2 hours and user clocks out 3 hours after their shift), then the clocking event would be discarded as invalid. These events will now be recorded as unknown and an administrator or manager may now deal with these events as they deem appropriate. |
|
WS-10080 |
Improved the account lockout feature to better protect against unauthorised access attempts. Account lockouts occur after multiple failed login attempts to help safeguard your data from brute-force attacks. These updates ensure stronger security while maintaining a smoother recovery process. Users will have a maximum of 5 attempts to enter their password correctly before their account will be locked. Accounts will now also automatically unlock after 5 minutes. |
Bug Fixes
|
JIRA Ref |
Description |
|---|---|
|
WS-10558 |
Resolved an issue in the PLAN screen where team shifts were not being cleared as expected. Previously, after confirming the date range for the shifts to be removed, the shifts would still appear in the plan view. This behavior has now been corrected—selected shifts will be properly removed as intended. |
|
WS-10539 |
Resolved an issue with the Employee report in MONITOR that would occasionally time out for clients with larger data sets. |
|
WS-10317 |
Resolved an issue where the search box on the PEOPLE page did not consistently return correct results when searching by both first name and surname together. Each column remains individually searchable, but only name and surname can now be reliably combined in a single search query. |
|
WTSSUP-231 |
Resolved an issue when deleting absences. The name of the person deleting the absence was not being recorded reliably in the shift history. In addition if comments were added, these were also not being saved. |
|
WS-10625 |
Resolved an issue with the ignore and proceed functionality. If removing a holiday or absence resulted in a Working Time regulations breach, the system would correctly prevent the removal of the absence, however if a user with the correct permissions attempted to “ignore and proceed”, this action resulted in no response and the absence remained. |
|
WS-10600 |
Resolved an issue with the role permissions screen. When removing The “View employees” permission, another permission “Variance report” was also being removed incorrectly. |
|
WS-10678 |
Resolved an issue with running the payroll report with a location selected. When a location is selected, the report does not return any data for accounts that should be included on the report. |
|
WS-10541 |
Resolved an issue with downloading into .csv format. Date formats were inconsistent and alternating between US and UK format. All .csv downloads (excel) should now be consistently in UK format. |
|
WS-10715 |
Resolved an issue with Reciprocal Shift Swaps where users clicking into the following month were presented with a loading screen and upon refresh, the current month was visible, thereby preventing a selection from the following month. |
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-10737 |
Resolved an issue causing the payroll report to time out when processing very large data sets. The payroll report will now run as a background process, similar to the accounts report, improving reliability and performance. This issue was identified during internal testing and cannot be reproduced in the live environment with the current data volume, so customers will not be able to recreate this issue. |