June 2023

Provide an Admin Interface that will allow configuring which gtfs routes an instances riders will be able to view. This ticket is to create a new admin tab that will let admins see all the available gtfs source/route combinations and decide which regions will be able to see which gtfs routes.

• Remove the ability to reserve a seat on a drop-off-only stop. Improve behavior to prevent reservations for dropoff-only stops including prompts in the Rider app and Rider web portal.
• Alter how `Driver manually increments ridership for Digital Tickets` is interpreted so that **only** pay boards are ignored. This is to improve back passenger boarding and digital ticketing data when drivers manually increment ridership via the tablet manifest.
• Add Is Escort Required to User Profile. This will allow a rider to specify if they should require an escort as part of their user profile. An escort can also be added when creating an anonymous trip.
• Add EndTime Param to GET/v1/boardingEvent API. Improving behavior by now allowing the entry of End Date/Time.

Protection Assignments Not Properly Splitting Stops on Unrolled Loop Routes - Release to Mainline. Correcting this behavior to properly represent split stops when using Protection on unrolled loops.

• Analyze Headway: Remove seconds from displayed times. Removing seconds from displayed time for a cleaner look.
• Planning & Analysis: Ability to Export Runs into .csv. We now have the ability to export new shifts in a format that vendors can read through and flag issues. The spreadsheet can be kept simple (shift, rides, breaks).  A new ‘Export as .csv’ button will now be visible at the top of the Calendar panel in the Planning tab.
• Rework the Optibus import so it doesn't require the GTFS trip ids. We now have the ability to utilize the duty id instead of the GTFS trip ids to find which trip is being referenced when importing Optibus data into our Planning & Analysis tool.
• Move the Optibus import behind an experiment flag. With the ability to import Optibus run cut data into the TripShot system, this ticket was implemented to hide this functionality behind an experiment flag (optibus).  This tool can only be utilized currently by customers that have both the optibus flag enabled, as well as the Planning & Analysis experiment flag (planning).

• Support Route Description in Admin Web. When creating a new route or editing an existing route, admin users now have the ability to add a ‘route description’.
• GTFS-RT Only Sending Real-Time Info for Active Rides. TripShot will now send GTFS-RT messages for rides in scheduled and accepted states, and not only for rides that are currently active or canceled.  With this update, if the vehicle on a ride is delayed, the GTFS-RT will indicate if the next ride for this vehicle will be delayed as well.
• For large customers, TripShot Admin > Assignment > Shift scroll bar is not working as intended. For customers with large amounts of data, the scroll bar within the Assignments tab will no longer be negatively impacted by the amount of data being loaded to the UI.
• Analyze Headway: Remove ETA coloring from Vehicle Icon. Customers utilizing the Analyze Headway tab will now only view vehicles on the Headway map with corresponding colors based on the vehicle assignment and the device status, rather than varying ETA colors.  As this tool is intended for non-time adherent stops on inexact loops, the ETA coloring for vehicles is unnecessary and has now been removed for just this map.  No other maps within the TripShot platform will be affected.
• SSO (OpenID) login will resync (at login) first/last name. This update will trigger the OpenID sync of first/last name fields when a user logs in via SSO as to match the current SAML behavior.
• Visualize differences in plan revisions via a .csv file. Clients utilizing the Planning & Analysis tool (currently in BETA) will now be able to easily visualize the differences between different optimizations of the same schedule/plan via a .csv file.
• Remove old badging format support and improve badge check tool to look into older badge files. The backend tool used to search badging counts and details has been updated/improved to more accurately represent consistent badge formatting.
• Azure Accessibility: 1.4.1 Use Of Color. This update is to correct accessibility guidelines regarding the coloring of areas within the Dispatch tab. These updates have previously been applied to all client instances; this release will now effectively update this coloring for Microsoft users.  
• Allow using OAuth2 to communicate with SFMTA. For clients utilizing SFMTA data, we have updated the API endpoint from OAuth to OAuth2.  This is a backend-only change that will not be felt by end users.
• Namespace Configuration (Rider ID column in Reservations Report). By enabling the experiment flag (alternate-rider-id), customers will now see the RiderID match to the corresponding Username field in Resources -> Users -> User.  This update will populate in the Reservations and Reservations By User Reports.

• Stop throwing errors on zero-length parking reservations. This update is to correct backend-only behavior when logging Parking Reservation data. This will not be felt by end users.
• GET /v1/shared/route is returning non-active internal routes even when startDay and endDay are specified. This update is to correct backend-only behavior to consolidate route grouping when shared routes are utilized.  This should not be felt by end users.
• Analytics CSV Download is resulting in 401. This update is to correct behavior for admin users when utilizing the Analytics report .csv download option.  Users will no longer experience any issues downloading this report.

'Unknown' text should not be displayed when admin attempts to save a reservation for the last stop on the 'Routes' page. This update is to correct behavior experienced by users attempting to reserve a ride on the last stop of a route.  Rider Web has now been updated with this fix, and Rider Apps will correct messaging in a future release to make riders aware that attempting to reserve rides on a dropoff-only stop at the end of a route is not possible.