Microsoft Teams
@everyone, VP wants us to update the passenger ticket modifiability from 4 hrs prior to departure to 1 hr. cc: @Haster please scope.@everyone, VP wants us to update the passenger ticket modifiability from 4 hrs prior to departure to 1 hr. cc: @Haster please scope.@everyone, VP wants us to update the passenger ticket modifiability from 4 hrs prior to departure to 1 hr. cc: @Haster please scope.
This is a moderately complex change affecting three core areas:This is a moderately complex change affecting three core areas:This is a moderately complex change affecting three core areas:
Fare rules §3.2Change the cutoff from 4 hours to 1 hour. @Katryn
Fare rules · §3.2, Ticket changes
- Current source
Tickets may be changed up to 4 hours before scheduled departure.- Proposed change
Tickets may be changed up to 1 hour before scheduled departure. Fare eligibility and change fees remain unchanged.
Commercial policy owner approves the new cutoff and its fare scope.
FLEX · changeCutoffHoursSet 4 → 1; keep other fare settings. @Jason
Fare setup · FLEX · changeCutoffHours
- Current source
changeCutoffHours = 4- Proposed change
changeCutoffHours = 1
Change the FLEX fare setting after approval; retain other fare settings.
change-eligibility.ts:18Read the fare cutoff instead of hard-coding 4. @Alia
change-eligibility.ts · line 18
- Current source
return fareAllowsChanges && hoursToDeparture >= 4;- Proposed change
return fareAllowsChanges && hoursToDeparture >= fare.changeCutoffHours;
Read the fare setting instead of keeping a second hard-coded cutoff.
Also review the six linked customer and operational sources.