- The app versions remain the same:
iOS: Native: 2.0.0, JS: 2.1.2
Android: Native: 2.0.0, JS: 2.1.2
No changes have been made to the app in the last two weeks.
Kura Status Page:
The Kura status page https://status.ridekura.com allows users to view operational status, incidents and scheduled maintenances on Kura systems, with live status updates.
You can select to receive incident or maintenance updates by email, by selecting the button at the top right of the page; 'SUBSCRIBE TO UPDATES'. You will be sent an email each time an incident or maintenance is added or an active status is updated. Please note that subscriptions are limited so this is for use by external customers only.
The status page also shows Kura systems uptime, upcoming scheduled release or maintenances and system response time metrics.
Past incidents, with steps taken to resolve, can also be viewed.
Kura Incident and Release Notifications:
Notifications will be shown on the Kura website, to inform users if there are any incidents that are affecting Kura performance or to let users know about an upcoming release.
The notification will display on the login page when a user is logged out of the Kura website, or on active page when a user is logged in to the Kura website.
The notification will be shown until it is dismissed.
The notification can be dismissed by selecting the 'x' in the top right corner.
Incidents, for example downtime or degraded performance, will be shown in Kura pink and will include a description of the incident and last updated time.
Scheduled release or maintenance notifications will be shown in Kura blue and include a description of the release or maintenance and scheduled timing.
These will display 24 hours before the scheduled maintenance window.
For both notification types, if you select the link 'View latest updates' you will be taken to a status page where you can view further details and actively monitor the incident or maintenance status. For releases, a link to the announcement section on zendesk will be included in the description, so that the release notes can be viewed.
Supplier Form Changes:
The supplier form has changed for trip schedules (Trips->Select Trip->Trip Calendar-> Edit Supplier), so that this allows sufficient space to accommodate supplier and driver names. This is now also consistent with editing supplier for an individual day so that there aren't two different forms to complete.
Add a supplier by selecting the 'ADD' button:
Select supplier, drivers, vehicles, enter capacity, select to and from dates and cost and sell prices as normal:
Supplier - Select Drivers:
The driver selection in the supplier form (Trips->Select Trip->Trip Calendar->Edit Supplier) or (Trips->Select Trip->Trip Calendar->Edit Trip->Supplier) previously listed all person profiles for an organisation. For organisations that use their own drivers, it was difficult to locate the required drivers from the list.
The supplier form now only contains users with an auth group in the primary and secondary driver drop-down lists.
The profiles in the drop-down lists are now also displayed in alphabetical order. Once the list is expanded you can type the first character(s) of the name and the list will move to show the selection, for example, typing 's' will take you to all first names starting with 's'.
Supplier - Select Supplier:
The supplier selection in the supplier form (Trips->Select Trip->Trip Calendar->Edit Supplier) or (Trips->Select Trip->Trip Calendar->Edit Trip->Supplier) now shows the organisation that the trip was created under at the top of the list, for self-serve organisations that will use their own drivers.
All other supplier organisations, that you have permission to view, are shown below this in alphabetical order, so that it is easier to find the supplier required. Once the list is expanded you can type the first character(s) of the supplier name and the list will move to show the selection, for example typing 's' will take you to all suppliers starting with 's'.
Client Booking change to Contracts:
There were mixed terms used in the website for contracts, as some views showed Client Booking and other showed Contract/s. All terms have now been updated for consistency, so you will see Contract/s throughout the website.
Confirmation Code Emails:
When a user creates their account they are sent a confirmation code to verify their account. The sending address for these emails has been changed from firstname.lastname@example.org to email@example.com to avoid these being sent to junk folders.
The email text has also been changed to better explain the next steps for a user and to provide a link to FAQ and support pages.
Magic Search Coachhire profiles:
If searching for names similar to those held in the coachhire organisation a permission error would be shown. This has now been resolved and coachhire profiles will not be included in search results.
No signal Alarm Trigger:
The no signal alarm trigger is not used so this has been removed. The trigger has been removed from any contract that had this configured.
Maintenance upgrade to the latest version of Typescript.
Old style APIs have been deprecated and unused query APIs have been removed.
The Quicksight data sync was causing timeouts, resulting in duplicate alarms for journeys being generated. A fix has been implemented but work will continue to set-up the triggers over multiple process, broken down into smaller parts, with the Quicksight data sync separated.
Changes released during the last 2 weeks:
The bookings export was not matching the date criteria selected from the calendar; the prior week to that selected was exported. This has been resolved and the week selected from the calendar will export.