Bug #3291
Android :-Implement Back to back trips
Added by Shalu T S over 1 year ago.
Updated 11 months ago.
Due date:
05/22/2025 (about 11 months late)
Milestone:
Sprint 24 Tukxi Ride 2024 Oct 01 to Oct 31
Branch name:
sprint-22_sreedevi_3291
Description
Back to back: Send trip request only when driver is nearby the drop off point
1. Trip details are not showing once accept the trip.
2. The driver can't message the passenger on the quid trip.
3. Driver can't call the passenger on the quid trip.
4. The rider can't message the driver for the quid trip.
Impact Analysis
UI Changes:
Addition of a new button to indicate the presence of a queued trip.
Display of a popup on button click, containing options for "Chat", "Call", "Cancel Trip Request", and location details.
The button needs to dynamically adjust its visibility based on whether a queue-trip is available.
Cancellation Handling:
If a queued trip is canceled, ensure that the trip is properly removed from the queue and the driver is notified.
Update both the driver and passenger about the trip cancellation in real-time, adjusting the system to reflect this change.
- Related to Bug #2753: Back to back: Send trip request only when driver is nearby the drop off point added
- Assignee changed from Jithin Kuriakose to Sreedevi K S
- Start date set to 09/05/2024
- Milestone deleted (
Backlog)
- Milestone set to Sprint 22 Tukxi Ride 2024 Aug 01 to Aug 31
- Branch name set to sprint-22_sreedevi_3291
- Description updated (diff)
- Due date set to 09/20/2024
- Status changed from New to In Progress
- Milestone deleted (
Sprint 22 Tukxi Ride 2024 Aug 01 to Aug 31)
- Milestone set to Sprint 23 Tukxi Ride 2024 Sept 01 to Sept 30
1. Add Temporary Icon to Toolbar for Q-Trip Indication:
- Implemented a temporary icon to indicate Q-Trip.
- Actions and visibility for Q-Trip are handled.
- The icon will be updated once the new design is ready.
2. Chat Option for Queue Trip:
- Chat option has been added for Q-Trip.
- Collaborated with the backend team to verify the push notifications for "CHAT."
3. Call Option (Ongoing):
- The implementation is currently in progress.
4. Change Visibility Handling of Q-Trip Button:
- The visibility of the Q-Trip button is now managed using local storage instead of data from `getDetail`.
- **Pending Subtask:** Requires 1–2 days to complete the implementation.
5. Implement New Design for Q-Trip Popup:
- **Pending Subtask:** The design implementation is pending and will take an estimated 1–2 days.
6. Unit Testing:
- **Pending:** Unit tests need to be implemented, which is estimated to take 1 day.
- Impact Analysis updated (diff)
- Due date changed from 09/20/2024 to 09/23/2024
- Due date changed from 09/23/2024 to 09/27/2024
- Status changed from In Progress to On Hold
- % Done changed from 0 to 90
- Milestone deleted (
Sprint 23 Tukxi Ride 2024 Sept 01 to Sept 30)
- Milestone set to Sprint 24 Tukxi Ride 2024 Oct 01 to Oct 31
- Status changed from On Hold to Resolved
UI part is incomplete and still wait for icons,UI from the team .
- Status changed from Resolved to QA Ready
- Due date changed from 09/27/2024 to 11/11/2024
- Status changed from QA Ready to QA In Progress
- Start date changed from 09/05/2024 to 11/11/2024
- Status changed from QA In Progress to QA Ready
1. Rider name is showing when the driver calls the rider for the trip that is in queue.
- Status changed from QA Ready to Reopened
- Status changed from Reopened to Resolved
1. Rider name is showing when the driver calls the rider for the trip that is in queue. : Fixed
- Status changed from Resolved to QA Ready
- Target version changed from 1.0.4 to 1.0.6
- Due date changed from 11/11/2024 to 05/19/2025
- Status changed from QA Ready to QA In Progress
- Start date changed from 11/11/2024 to 05/19/2025
- Due date changed from 05/19/2025 to 05/21/2025
- Start date changed from 05/19/2025 to 05/21/2025
- Due date changed from 05/21/2025 to 05/22/2025
- Status changed from QA In Progress to Reopened
1. Queued trip is not showing in the driver once the 1st trip ends.
2. Previous chats (Unwanted messages) showing in the trip chat.
3. Call not received to the driver app.
4. The message send from rider is not received to the driver.
Also available in: Atom
PDF