Project

General

Profile

Actions

Feature #33194

open

Flight Module | Combination Flow Integration

Added by Anjana Krishnan 2 months ago. Updated about 2 months ago.

Status:
Fixed not Tested
Priority:
Normal
Target version:
-
Start date:
02/17/2026
Due date:
02/25/2026 (48 days late)
% Done:

100%

Estimated time:
Spent time:
remarks:
DB Changes:
Keys & Permissions:
Areas Affected:
Files Changed:

Description

Flight module combination flow integration

Actions #1

Updated by John Pius Thayiparampil 2 months ago

  • Status changed from Assigned to In Progress
Actions #2

Updated by John Pius Thayiparampil 2 months ago

integration inprogress ,combaining into a single folder

Actions #3

Updated by John Pius Thayiparampil 2 months ago

  • % Done changed from 0 to 20

completed the module integration , now rectifing the errors in the module

Actions #4

Updated by John Pius Thayiparampil 2 months ago

  • % Done changed from 20 to 40

Compeleted the integretion , unit test on going , but still on older design , need to change the complete ui and entire modules

Actions #5

Updated by John Pius Thayiparampil 2 months ago

working on the design changes and workflow issues in the flight combination and normal modules

Actions #6

Updated by John Pius Thayiparampil 2 months ago

resolved the search issue , working on design issues

Actions #7

Updated by John Pius Thayiparampil 2 months ago

ongoing module integration - design changes in home , search and result , sort completed , working on the flow change and design changes

Actions #8

Updated by John Pius Thayiparampil 2 months ago

  • Due date changed from 02/12/2026 to 02/13/2026

ongoing module integration - design changes in fare summary , fare rule , fare details, modify search, filter and branded fare screen.

Actions #9

Updated by John Pius Thayiparampil about 2 months ago

  • Due date changed from 02/13/2026 to 02/16/2026
  • % Done changed from 40 to 70

completed the entire pax page ,detailed view ,functionality and design

Actions #10

Updated by John Pius Thayiparampil about 2 months ago

  • Due date changed from 02/16/2026 to 02/17/2026
  • Start date changed from 02/05/2026 to 02/17/2026
  • % Done changed from 70 to 80
Actions #11

Updated by John Pius Thayiparampil about 2 months ago

development in progress, completed the seat mapping screen, functionality changes in result screen , pax screen , payment gateway and flow change in refund protector flow change in the flight details page.

Actions #12

Updated by John Pius Thayiparampil about 2 months ago

  • Due date changed from 02/17/2026 to 02/18/2026
Actions #13

Updated by John Pius Thayiparampil about 2 months ago

completed the payment screen integreation , branded fare bug issue , completed the bug fixing in the search screen, setted up the home screen launcher , in progress in payment gateway

Actions #14

Updated by John Pius Thayiparampil about 2 months ago

  • Due date changed from 02/18/2026 to 02/19/2026
Actions #15

Updated by John Pius Thayiparampil about 2 months ago

All its logic (API calls, combo flight building, WhatsApp charge) was added into the Pax screen so the Details screen now just redirects straight to Pax, eliminating a duplicate getFlightDetail() API call that was causing 400 errors.
It now handles everything: building flight details, WhatsApp charge, combo flow (getLinkFlight - getFlightConfirm - getFlightFare), and all passenger init calls in one place.
The combo payment flow was passing WebViewPaymentArgs but the router was casting it to WebViewParams, causing a type cast error that crashed the app.
reordered sections (Baggage → Features → Meals → Cabin → Fare Type), added "no meals" fallback, updated to ic_branded_tick

Actions #16

Updated by John Pius Thayiparampil about 2 months ago

  • Due date changed from 02/19/2026 to 02/20/2026
Actions #17

Updated by John Pius Thayiparampil about 2 months ago

  • % Done changed from 80 to 90

integrating a Combination Flights module - fixed payment gateway issues with the webview and the controller , fixed the flow issues in the payment screen , design change in ticket screen , ticket failed screen booking fail screen. completed the code conflict issues got resolved .

Actions #18

Updated by John Pius Thayiparampil about 2 months ago

  • Due date changed from 02/20/2026 to 02/23/2026
Actions #19

Updated by John Pius Thayiparampil about 2 months ago

completed the unit testing with yabila api , completed the setions

Actions #20

Updated by John Pius Thayiparampil about 2 months ago

  • Due date changed from 02/23/2026 to 02/24/2026
  • Status changed from In Progress to Fixed not Tested

completed the configured with qgoonline api call on the app.completed module

Actions #21

Updated by John Pius Thayiparampil about 2 months ago

  • Status changed from Fixed not Tested to In Progress
Actions #22

Updated by John Pius Thayiparampil about 2 months ago

  • Due date changed from 02/24/2026 to 02/25/2026
Actions #23

Updated by John Pius Thayiparampil about 2 months ago

  • Status changed from In Progress to Fixed not Tested
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF