August 2022

• Support editing Parking reservations. As a Rider, I need to edit my parking reservation without the system deleting my previous request, putting my reservation at the end of the waitlist. Our goal is to define which edits are acceptable and which edits will trigger a new reservation:
  1. Changing from 9-10 to 10-11 would be a new request.
  2. But changing from 9-11 to 10-11 would be a minor modification and shouldn't impact the rider.
  3. If someone modifies the vehicle it would be a minor modification and it shouldn't modify the confirmed reservation or place in line.
  4. If I update the space type - it becomes a new request.
• A11y remediation: Use button trait on region picker screen. Accessibility Improvements.
• Wrap Region text within slideout menu.

• Fix app crashes when the app is backgrounded. We are seeing a lot of Android Driver app crashes on Android 12. They are related to how we keep the Driver app running all the time, even if it is minimized (put into the background). When we try to start the foreground service from DriverApplication#onCreate, the app might not technically be in the foreground yet. Since we already listen for foreground/background events in the Driver application, we will tie the start of the foreground service (DriverService) to that callback.

• Driver Tablets Are Displaying Shifts in Inverse Order. Fixes, Shifts are being displayed as inverted with later services and rides on top of the current/more recent services.

• Prompt User for App Store feedback after OnDemand feedback. Android component for prompting Rider app store feedback when the following occurs:
  1. On-Demand trip was completed successfully
  2. Rider gives 5-star review of their OD trip (within TripShot app)
  3. Rider will now get asked to provide a review on the App Store.
• Support editing Parking reservations. As a Rider, I need to edit my parking reservation without the system deleting my previous request, putting my reservation at the end of the waitlist. Our goal is to define which edits are acceptable and which edits will trigger a new reservation:
  1. Changing from 9-10 to 10-11 would be a new request.
  2. But changing from 9-11 to 10-11 would be a minor modification and shouldn't impact the rider.
  3. If someone modifies the vehicle it would be a minor modification and it shouldn't modify the confirmed reservation or place in line.
  4. If I update the space type - it becomes a new request.
• A11y remediation: Improve Android text field hint contrast. Accessibility Improvements.
• A11y remediation: Improve Android tab contrast. Accessibility Improvements.
• Wrap Region text within slideout menu.

• Add a reasonable maximum size for parking lots. Creating a parking lot involves an algorithm that can lead to timeouts if a ridiculous number is entered for parking lot spaces. Parking Lot spaces will be capped at 20,000.

• User creation ignores some `AutoUserGroup`s. Fixes, Creating a user when there is an auto_user_group (not exposed to admins) that matches only the user's namespace will not cause the user to be added to the wallet user group.

• System should auto cancel Parking Reservation if not checked-in after 60 minutes start time. When a user makes a Parking Reservation and does not "check-in" at scheduled time the reservation is never auto canceled until 30 min past the scheduled end time. This means the parking space is "not used" and is not given back to the pool until the end time.

New:

• Documentation for API endpoint /v2/parking/lot.
• Password Reset option for Users page in the Admin Console. The Admin role will have access to a "Reset Password" button on a users account page. Clicking this button would allow the creation of a "Temp" Password so the user can login, update their contact information and reset the password via the reset password email available from the app and web app.

• Assignments page is performing too much work after network call. Performance Improvement.
• Remove restriction for OnDemand schedule ahead of 30 days. Now On Demand services can be scheduled for 180 days in advance by selecting the value under the "Allow rides up to xx days xx hours xx minutes in the future " section on the 'On Demand>>Services' page. Validation message "Ride time cannot be more than 180 days." is correctly displayed if the user provides the value of more than 180 days under the "Allow rides up to xx days xx hours xx minutes in the future " section.

• Times in Parking Reports are not showing up correctly. The timezone displayed on the web report is controlled by the timezone box in the upper right, not the region box.