ToDoListItems
| Id | 507 |
|---|---|
| Task | <p><strong>Feedback on Transfer Macro</strong></p><ul><li>The time box should be a format for time (24hrs) and width should match the dates</li><li>Date should show the DoW (eg Sun 16 May 2025) <strong>TODO</strong></li><li>Destination<ul><li>Should be sorted by “SortOder” and then alphabetically on "City"- with a break before ‘20’ <strong>TODO</strong></li></ul></li><li>Handling Destination is a "Train Station"<ul><li>If you change the Destination from a City to a train/airport (eg from Verbier to Martigny Train) then the From Address field should switch to Train time/Flight </li></ul></li><li>When Destination is a City (eg Verbier), the Accommodation dropdown needs to contain all the information (see attached screenshot). 2 lines required for each address: <ul><li>Symbol to indicate the “Type”<ul><li>‘House’ for a Chalet</li><li>‘Knife and fork’ for a Restaurant</li><li>‘Office building’ for a Hotel</li></ul></li><li>Then show the Chalet Name, Apartment details, and then the Affiliate (in brackets)</li><li>Then line below should have the street and house number</li></ul></li><li>Looking at the database entry for the Transfer:<ul><li>PassengerName and PassengerEmail and PassengerMobile should not be inherited from the Booking. <ul><li>This is an over-ride should the transfer not be in the name of the Booking. So unless populated manully, it should be null</li></ul></li><li>Trip date should be not nullable. Time should not be nullable but have a TBD over-ride or (TBD checkbox)</li><li>Should we rename TripXX to TransferXX in all the fields?</li><li>The addressStart and addressEnd still seems to be a string field rather than a relation field related to the Accommodation entity<ul><li>We need this to be linked because the driver will be given various info points from the Accommodation entity (eg Door Code, GPS location, Driver notes, Client notes, Associated Resort Contact). But there neeeds to be a manual over-ride “Other” available</li></ul></li></ul></li><li>Layout of Pax Child/baby. Try to get on 1 line</li></ul><p> </p><ul><li>The Hide/Show extra fields<ul><li>The Passenger Name/Email/Mobile should be here. (These are the “over-ride ones in case the names is not the same as the Passenger details for the ”Booking" as a whole</li><li>Delete Button should be hidden</li><li>There should be a “Cancel trip flag” - which is similar to delete but retains the info for document record keeping purposes</li><li>Notes needs to be a bigger field</li><li>The timestamps can be indicated in pop-ups without expanding the section. The user will only expand if they want to edit - which is rare as the times are generated by the system.</li></ul></li></ul><p> </p><p>Feedback on the Booking section (on the left)</p><ul><li>When you save the booking, you should show the ID of the “Booking”. This is the customer reference number</li><li>Client email and client mobile should be nullable</li><li>Client details should be saved in the Clients entity if unique (ie that database grows) </li><li>Status should be: Confirmed/Inquiry/Cancelled (no need for cancel booking field)</li><li>Booking history: This should save the logged-user and time of creation</li><li>Payment link expiry: First trip date time less 24 hours</li><li>Still has the word “Transfers” on the bottom left</li></ul><p> </p><p> </p> |
| Status | Complete |
| Priority | 10 |