Oriol Roqué Paniagua 4f6728003a Merged PR 2029: Guest Journey - start date based on used link ... Added verification estimated started at/date utc. Ensured continuity for existing reports I also noticed I missed one propagation of the end date, it's fixed here. Note: changed the naming from 'start' to 'started' since we already had 'completed' and 'used_link' Related work items: #17268		2024-06-13 14:53:58 +00:00
..
int_core__booking_charge_events.sql	Merged PR 2029: Guest Journey - start date based on used link	2024-06-13 14:53:58 +00:00
int_core__bookings.sql	a few quick and dirty improvements	2024-05-10 00:31:27 +02:00
int_core__check_in_cover_prices.sql	propagating renames	2024-05-08 12:03:44 +02:00
int_core__deal_id_master_list.sql	docs and moving stuff	2024-04-08 09:44:32 +02:00
int_core__duplicate_bookings.sql	a few quick and dirty improvements	2024-05-10 00:31:27 +02:00
int_core__mtd_aggregated_metrics.sql	Merged PR 2003: Business KPIs first draft	2024-06-11 15:45:57 +00:00
int_core__mtd_booking_metrics.sql	Merged PR 2003: Business KPIs first draft	2024-06-11 15:45:57 +00:00
int_core__price_plans.sql	docs and moving stuff	2024-04-08 09:44:32 +02:00
int_core__unified_user.sql	add phone number	2024-06-10 16:14:07 +02:00
int_core__verification_payments.sql	moving forward with the checkincover specific model	2024-04-26 16:45:43 +02:00
int_core__verification_request_completed_date.sql	Merged PR 2028: guest journey estimated completed date	2024-06-13 13:30:22 +00:00
int_core__verification_request_completeness.sql	Merged PR 2020: Verification request completeness for intermediate steps + schema documentation	2024-06-13 08:14:11 +00:00
int_core__verification_requests.sql	Merged PR 2029: Guest Journey - start date based on used link	2024-06-13 14:53:58 +00:00
int_core__vr_check_in_cover.sql	Merged PR 2029: Guest Journey - start date based on used link	2024-06-13 14:53:58 +00:00
schema.yaml	Merged PR 2028: guest journey estimated completed date	2024-06-13 13:30:22 +00:00