Project

General

Profile

Bug #3039

For multiple destination trips, the kilometer calculation is wrong.

Added by Shalu T S almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
07/04/2024
Due date:
12/03/2024
% Done:

100%

Estimated time:
Milestone:
Sprint 21 Tukxi Ride 2024 July 01 to July 31
Branch name:
sprint-20_anandhu_3039

Description

For multiple destination trips, the kilometer calculation is wrong. starting and ending positions are only considered for the final amount calculation. actually want to consider the whole travel distance for amount calculation.

STR.
1. Open the rider app.
2. Request a round trip.
3. Accept and complete the trip.
4. Check the fare amount.

ER.
4. Amount should be calculated based on the total distance traveled.

AR
4. Only consider the distance between the start and end point.


Files


Impact Analysis

Google direction api is calling to get the distance when ending the trip everytime and comparing the trip distance with the distance returned by direction api call. Changed the direction api call to add multiple destinations as waypoints, if the trip has multiple destinations then the location is passing to the direction api call and calculating the distance include of the multiple destinations.

#1

Updated by Jithin Kuriakose almost 2 years ago

  • Branch name set to sprint-20_anandhu_3039
#2

Updated by Anandhu P Kumar over 1 year ago

  • Status changed from New to Resolved
  • Start date set to 07/04/2024
  • % Done changed from 0 to 100
  • Impact Analysis updated (diff)

Changed the google direction api call to add stops as waypoints to get the distance include the stops.

#3

Updated by Jithin Kuriakose over 1 year ago

  • Status changed from Resolved to QA Ready
#4

Updated by Shalu T S over 1 year ago

  • Status changed from QA Ready to Reopened

1. The distance showing in the ride request popup is not correct for multiple stops trips.
2. The estimated amount is not correct in rider request popup, for multiple stops trips.

#5

Updated by Anandhu P Kumar over 1 year ago

  • Status changed from Reopened to Resolved

The distance showing in the popup in driver app is calculated from the front end, The reason for the wrong distance is that there is no waypoints passing in the google direction api call in the front end.

#6

Updated by Jithin Kuriakose over 1 year ago

  • Status changed from Resolved to QA Ready
#7

Updated by Shalu T S over 1 year ago

1. The distance showing in the ride request popup is not correct for multiple stops trips. : Fixed
2. The estimated amount is not correct in rider request popup, for multiple stops trips. : Fixed

#9

Updated by Shalu T S over 1 year ago

  • Due date set to 12/03/2024
  • Status changed from QA Passed to Closed

Also available in: Atom PDF