Support #25749: Review | Need API changes and correction for Train module - Almaqam-Final Phase-Web - Redmine

Actions

Copy link

Support #25749

open

Feature #22066: Train Module Integration | HaramainTrain || Search to ticketing and my booking

Review | Need API changes and correction for Train module

Added by Vivek V 4 months ago. Updated 2 months ago.

Status:

Completed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

08/11/2025

Due date:

08/14/2025 (about 3 months late)

% Done:

100%

Estimated time:

3:00 h

Spent time:

12:30 h

remarks:

DB Changes:

Keys & Permissions:

Areas Affected:

Files Changed:

Description

1 While adding multiple passengers, in the payment progress page, the API (ticket poll) response is returning true only and is not changing to false.
2 For b2b and inhouse the submitpax is getting internal server error.
3 On the Pax page, the API response for a round trip provides only the TotalAmount in the FareDetails. As a result, we are unable to display the outbound and return train fares separately in the fare breakdown.
4 The strike-off amount is currently shown only for the total amount. We also need the strike-off amount to be shown per passenger.
5 In the response of ticket in the passenger section the TickerNumber is getting null.
6 In the ticket page when i click Save getting internal server error.
7 Email not getting in the d1 need to check in qa2

Actions

Copy link

Updated by Vivek V 4 months ago

Subject changed from Need API changes and correction for Train module to Review | Need API changes and correction for Train module

Actions

Copy link

Updated by Sandeep Sajiv 3 months ago

Due date set to 08/11/2025
Status changed from New to Assigned
Assignee set to Adarsh K K
Start date changed from 08/08/2025 to 08/11/2025
Estimated time changed from 0:00 h to 3:00 h

Actions

Copy link

Updated by Adarsh K K 3 months ago

Status changed from Assigned to In Progress

Actions

Copy link

Updated by Adarsh K K 3 months ago

1) as of now some time only the booking and ticketing response getting from provider some times getting as error
2) issue fixed

Actions

Copy link

Updated by Sandeep Sajiv 3 months ago

Due date changed from 08/11/2025 to 08/12/2025

Actions

Copy link

Updated by Adarsh K K 3 months ago

% Done changed from 0 to 70

1 as of now some time only the booking and ticketing response getting from provider some times getting as error under escalation
2 issue fixed
3 fares passing as combined, no individual brake down, fixed
4 passing strike-off amount for per passenger. fixed
5 Ticket Number and additional data's added. fixed
6 create server ticket URL for train. fixed
7 Email not implemented in train

Actions

Copy link

Updated by Adarsh K K 3 months ago

6>>create server ticket URL for train. need fix from frontend

Actions

Copy link

Updated by Jithin J 3 months ago

Due date changed from 08/12/2025 to 08/14/2025

Actions

Copy link

Updated by Adarsh K K 3 months ago

Status changed from In Progress to For Review
Assignee changed from Adarsh K K to Sandeep Sajiv
% Done changed from 70 to 100

please assign to frontend
1 fixed multipax ticketing fail issue
2 issue fixed
3 fares passing as combined, no individual brake down, fixed
4 passing strike-off amount for per passenger. fixed
5 Ticket Number and additional data's added. fixed
6 create server ticket URL for train. fixed
7 Email implemented

6>>create server ticket URL for train. need fix from frontend

Actions

Copy link

#10