Bug 473172

Summary:	Enhancement Request: Switchable Connection Search Fields and Recently Searched Connections Feature
Product:	[Applications] KDE Itinerary	Reporter:	reportthebug <chris.seiferth>
Component:	general	Assignee:	Volker Krause <vkrause>
Status:	REPORTED ---
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	All
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description reportthebug 2023-08-08 20:44:34 UTC

I would like to submit a feature request to improve the user experience when searching for connections in the KDE Itinerary application. I would like to request the addition of two features:

1. Switchable connection search fields:

It would be helpful if the application offered a switchable option to swap the "From" and "To" fields in the connection search fields. This would allow users to quickly enter their origin and destination without having to manually rearrange the fields, saving time and effort.

2. Recently searched connections feature:

It is already possible to view a list of recently searched (train) stations. However, a quicker addition would be to implement a feature that displays a list of recently searched connections. This would allow users to easily access and reference their previous search results with one click, reducing the need to re-enter the same information. 

What do you think?

Comment 1 Volker Krause 2023-08-09 15:33:27 UTC

This makes sense in general, but also lets me suspect that the existing features to avoid the need for any of that aren't working. The search form is supposed to be pre-filled with the location and date of the current timeline position. So the idea is that you usually would only need to adjust the time and destination.

If that's not happening we need to fix it. If however your usage pattern or usecase isn't covered by that it would be interesting to learn more about how you use this feature to better understand how to support that best.

Comment 2 reportthebug 2023-08-12 20:39:20 UTC

(In reply to Volker Krause from comment #1)
> This makes sense in general, but also lets me suspect that the existing
> features to avoid the need for any of that aren't working. The search form
> is supposed to be pre-filled with the location and date of the current
> timeline position. So the idea is that you usually would only need to adjust
> the time and destination.
> 
> If that's not happening we need to fix it. If however your usage pattern or
> usecase isn't covered by that it would be interesting to learn more about
> how you use this feature to better understand how to support that best.

My use case would be to search for the same direction several times after searching for another connection. When I search for a connection from point A to B, for example in the Öffi app, this is saved in a kind of history at the bottom of the search field, where I can then simply click on a last search route.

See the picture: https://my.adminforge.de/apps/files_sharing/publicpreview/MgnaBNMSFxqMoSD?file=/&fileId=1576156&x=1366&y=768&a=true&etag=f96025a514e7938066b8003724eabbcc

Comment 3 Volker Krause 2023-08-14 15:09:33 UTC

Ah, so you are mainly using this to search for connections, but aren't storing them in the timeline? For that the current UI indeed isn't great.