Bug 462742

Summary:	Android: Trip interpreted in reverse order
Product:	[Applications] KDE Itinerary	Reporter:	Lukas Spies <Lukas>
Component:	general	Assignee:	Volker Krause <vkrause>
Status:	REPORTED ---
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Android
OS:	Android 11.x
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Lukas Spies 2022-12-07 14:40:46 UTC

SUMMARY

I'm travelling from Germany via Belgium to France. I have two tickets, one from Germany to Belgium (through DB) and one from Belgium to France (through SNCF), both coming from a single booking. The Android app properly detects that they are part of the same trip, but it interprets this as a trip from France to Germany and has the two tickets in reverse order, even though the times and everything are detected correctly. As a quick "fix", is there an option I missed to have the tickets not grouped?

STEPS TO REPRODUCE
1. Import ticket from DB for Germany to Belgium
2. Import ticket from SNCF for Belgium to France 

OBSERVED RESULT
The trip is interpreted in reverse order.

EXPECTED RESULT
The trip is interpreted in the right order.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Volker Krause 2022-12-08 16:52:37 UTC

The most common case for this is missing times when extracting the data, either because only the barcodes were detected (which typically don't have that information), or because of the tickets not having that information at all (tickets not bound to a specific train).

The easiest way to fix this is usually selecting "Alternatives" on the details page for the affected train trip and picking the right connection from there.

Investigating why the times are not detected if they are included in the tickets would likely require access to the corresponding tickets though.