id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
24516	Improve Autocompletion	GerdP	team	"When tagging guidepost I often have to enter several tag keys like 
`direction_north=*`, `direction_north:route=*`, and `direction_north:symbol`, followed by similar tags for other directions. Sometimes I only need `direction=*`
Autocompletion too often suggests the longest match, e.g. when I start typing `dir` it may suggest key `direction_northwest:symbol` instead of only `direction`. 
I typically have to either type a lot more characters or I use the cursor to get to wanted position. Both are time consuming.
Is there an option to tell JOSM that it should use the shortest match instead? So, e.g. suggest 
`direction` when typing dir, and then, after typing ""_n"" it should suggest `direction_north`.
I think I have the same problem with tag keys like `bicycle:left:surface`, `bicycle:left:traffic_sign` etc.

If there is no such option: Wouldn't it be better to do this by default?

I think the same is true for tag values, e.g. the value for `direction_northwest:symbol` can be
`train_station;none;train_station`. Now, when I tag a differnt guidepost and enter the value for tag `direction_northwest:symbol` JOSM might suggest `train_station;none;train_station` instead of only `train_station` when I start typing ""t"" assuming that there is a tag `direction_northwest:symbol=train_station` in the data or in the presets. 

Addition 1: Some tags like survey:date or check_date or start_date contain dates or years. It would be good if JOSM would sort those so that the oldest date comes last in the list of known values instead of sorting the values alphabetically (-> oldest date comes first). This is also a good idea for all tags with prefixes like check_date: and maybe also with suffixes like :date. 
Addition 2: The autocompletion text field for the upload comment should also use the most recent matching entry instead of the first in a list which seems to be sorted alphabetically. This is a problem when JOSM decides to empty the field because of preference `upload.comment.max-age` which is set to 14400 seconds (4 hours) by default.
I've quite often not noticed this problem and uploaded with the wrong comment."	enhancement	closed	normal	26.03	Core		fixed