Contents
- DRS-9913 - Daily Schedule Types have not mapped over on the data import."
- DRS-9912 - Working Hours Calendar ID field does not map to the same sentence case.
- DRS-9916 - Abilities and Sectors are not showing all assigned values when selecting the column in a list. This should be a comma separated list.
- DRS-9917 - Duration Adjustment is showing as a decimal, rather than the full value.
- DRS-9918 - Creation Date is not a selectable field within the view selector
- DRS-9919 - Priority field is showing with an _ in view columns.
- DRS-9920 - When loading data from DRS 6, sectors are not being mapped to the Agencies as they are in DRS 6
- DRS-9921 - Shared views are not assigned to Profiles on the data import.
- DRS-9922 - External Charts are not mapped on DRS 6 Imports
- DRS-9924 - An error is displayed on Customers if no template is set.
- DRS-9938 - When attempting to share a bookmark, an error is being displayed including the Name of the bookmark suggesting it cannot be found
- DRS-9939 - When attempting to change operative from the right click on the diary, DRS was showing an unspecified error
- DRS-9940 - Update Comments box errors when attempting to do anything and display quality is poor.
- DRS-9941 - When using the DRS template export format from the View, an error is displayed.
- DRS-9943 - When attempting to load bulk jobs, an error was being displayed by the WebService Gateway Bridge
- DRS-9966 - Inconsistent Error when creating views
DRS 7 Beta Fixes
Updated
by Andrew Dotto
- DRS-9913 - Daily Schedule Types have not mapped over on the data import."
- DRS-9912 - Working Hours Calendar ID field does not map to the same sentence case.
- DRS-9916 - Abilities and Sectors are not showing all assigned values when selecting the column in a list. This should be a comma separated list.
- DRS-9917 - Duration Adjustment is showing as a decimal, rather than the full value.
- DRS-9918 - Creation Date is not a selectable field within the view selector
- DRS-9919 - Priority field is showing with an _ in view columns.
- DRS-9920 - When loading data from DRS 6, sectors are not being mapped to the Agencies as they are in DRS 6
- DRS-9921 - Shared views are not assigned to Profiles on the data import.
- DRS-9922 - External Charts are not mapped on DRS 6 Imports
- DRS-9924 - An error is displayed on Customers if no template is set.
- DRS-9938 - When attempting to share a bookmark, an error is being displayed including the Name of the bookmark suggesting it cannot be found
- DRS-9939 - When attempting to change operative from the right click on the diary, DRS was showing an unspecified error
- DRS-9940 - Update Comments box errors when attempting to do anything and display quality is poor.
- DRS-9941 - When using the DRS template export format from the View, an error is displayed.
- DRS-9943 - When attempting to load bulk jobs, an error was being displayed by the WebService Gateway Bridge
- DRS-9966 - Inconsistent Error when creating views
As part of the DRS 7 BETA Testing and releases, then following fixes have been deployed into our Production Environments.
Type | JIRA - Description | Comment/Fix | Resolved | Resolution Date |
Issue | DRS-9913 - Daily Schedule Types have not mapped over on the data import." | Data import was checked and this was verified. Changes have been made to ensure that both Daily Schedule Types and any calendars marked as Rosters are imported and key IDENT fields have been correctly mapped | Yes, change implemented | 29/04/2026 |
Issue | DRS-9912 - Working Hours Calendar ID field does not map to the same sentence case. | All ID fields in DRS 7 will now have the format of ALL CAPS and UNDERSCORES for space fields. This is by design to ensure data integrity. Name fields will map as configured in DRS 6 to ensure user experience is unchanged. | No. Issue rejected | 29/04/2026 |
Issue | DRS-9916 - Abilities and Sectors are not showing all assigned values when selecting the column in a list. This should be a comma separated list. | The display of Abilities has been addressed, which will now display abilities in a comma separated list. Displaying Sectors as a Comma Separated Value has yet to be resolved, this will be followed up. | Yes, Partial Change Implemented | 29/04/2026 |
Issue | DRS-9923 Advanced Filtering is not working as intended when using Wildcards in Views | Warnings and Errors in the SQL were being incorrectly supressed and when the full SQL was built with the view, no data was returned. DRS will now attempt to correct for bad SQL results and log issues to Administrators for review | Yes, change implemented. | 30/04/2026 |
Issue | DRS-9917 - Duration Adjustment is showing as a decimal, rather than the full value. | A change has been implemented to display the efficiency modifier as a full value as with DRS 6 | Yes, change Implemented | 29/04/2026 |
Issue | DRS-9918 - Creation Date is not a selectable field within the view selector | The column ha s now been added, as has other objects from the Action History. | Yes, change implemented | 29/04/2026 |
Issue | DRS-9919 - Priority field is showing with an _ in view columns. | The column mapped to the view field for Priority was the IDENT field. This has been updated to display the NAME field. | Yes, change implemented | 29/04/2026 |
Issue | DRS-9920 - When loading data from DRS 6, sectors are not being mapped to the Agencies as they are in DRS 6 | A change has been implemented to ensure sectors are mapped on data import. | Yes, change implemented | 29/04/2026 |
Issue | DRS-9921 - Shared views are not assigned to Profiles on the data import. | An issue was found where the wrong idents were being assigned on the data load. This has now been resolved and views will be appropriately assigned on import. | Yes, change implemented | 29/04/2026 |
Issue | DRS-9922 - External Charts are not mapped on DRS 6 Imports | External charts are not being imported as part of DRS 7 build due to the changes of data source with DRS 7. | No. Issue rejected | 29/04/2026 |
Issue | DRS-9924 - An error is displayed on Customers if no template is set. | This is a data issue in DRS 6. If there is no template assigned to a customer in DRS 6, none will be applied to the Customer on the data load as this may effect integrity. All customers who are being onboarded will need at least one Default Customer Template to ensure that new customers created have a template applied. This will not effect data integrity. | No. Issue rejected | 29/04/2026 |
Issue | DRS-9938 - When attempting to share a bookmark, an error is being displayed including the Name of the bookmark suggesting it cannot be found | A change has been made to ensure the share request is using the ID of the bookmark rather than the name in the share request. | Yes, change implemented | 29/04/2026 |
Issue | DRS-9939 - When attempting to change operative from the right click on the diary, DRS was showing an unspecified error | An issue was found where the worker selector was not being requested correctly. This has now been resolved. | Yes, change implemented | 29/04/2026 |
Issue | DRS-9940 - Update Comments box errors when attempting to do anything and display quality is poor. | Changes have been made to ensure that comments will now be saved. Display is still poor. This is being picked up by a separate ticket. | Yes, partial change implemented. | 30/04/2026 |
Issue | DRS-9941 - When using the DRS template export format from the View, an error is displayed. | An issue was found in a code library used to encode the export file. This has been updated. | Yes, change implemented | 30/04/2026 |
Issue | DRS-9943 - When attempting to load bulk jobs, an error was being displayed by the WebService Gateway Bridge | Increases in data management and validation has resulted in tighter restrictions on what can be provided to the WebService Gateway Bridge. A change has been made to allow for lighter validation rules to support the backwards compatibility. | Yes, change implemented | 30/04/2026 |
Issue | DRS-9966 - Inconsistent Error when creating views | DRS is displaying an error when trying to add some columns to the views. It was found that the view request was missing an encapsulation. This has been resolved. | Yes, change implemented | 12/05/2026 |
Issue | DRS-9963 - When editing Follow On Templates, selectable detail is not available | An error was found when DRS was attempting to read from the selectable Custom Data lists. This was preventing selectable data from being displayed. This has been resolved. | Yes, change implemented | 12/05/2026 |
Issue | DRS-9957 - Attempting to remove an unavailability from the diary returns an unknown error | The deleteUnavailbility request was looking at the wrong BusinessLayer request to commit the change. This has been resolved. | Yes, change implemented. | 12/05/2026 |
Issue | DRS-9965 Jobs created by bridge have name field mis-mapped | Fields have been remapped to ensure Name field maps to primary order number. | Yes, change implemented. Limited Testing available | 12/05/2026 |
Issue | DRS-9956 Abilities and Sectors are shown over a number of different | Columns now have been aligned to consolidate the assigned values | Yes, change implemented. | 12/05/2026 |
Issue | DRS-9949 Day Off Calendar cannot create Day Off Type | Day off calendar was not validating time values correctly. This has now been resolved. | Yes, change implemented | 12/05/2026 |
Issue | DRS-9948 Luncbreaks in Daily Schedule Types must be full length of lunch window. This should be up to and including. | Day off calendar was not validating time values correctly. This has now been resolved. | Yes, change implemented | 12/05/2026 |
Issue | DRS-9947 Efficiency Modifier in the column view should be a whole number, no decimals | This field has now been set as a whole number with no decimal place. | Yes, change implemented | 12/05/2026 |
Issue | DRS-9942 Defaults are not saving when changed on shared views | An issue was being caused by validation when multiple defaults were set. This has now been resolved and defaults will save as expected. | Yes, change implemented | 12/05/2026 |
Issue | DRS-9939 - Change Operative is showing an unknown error | The error was caused because a null was recieved when a possible operatives check was made. Now if no operatives are available for the request, an appropriate error will be displayed. | Yes, change implemented | 12/05/2026 |