id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
17897	relation editor: sorting and directions with forward/backward not working properly.	skyper	team	"==== What steps will reproduce the problem?
1. open a 2-way route relation with some members with role forward/backward
1. select all members and sort them

==== What is the expected result?
I get a well sorted relation with full connection and direction indication

==== What happens instead?
* Sort does not always work, especially, if there are more than one way to sort it and only one way is accepted
* Perfectly sorted members are rearranged (see above) and connectivity is rendered wrong (not connected)
* the direction of oneway is interpreted wrong

==== Please provide any additional information below. Attach a screenshot if possible.
* I made a small [attachment:josm_17897_example.osm.xz example file].
* moving some members down/up helps sometimes.
* reversing simple relations like in the example should also be correct but JOSM does not like them.

{{{
URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-07-07 14:17:28 +0200 (Sun, 07 Jul 2019)
Build-Date:2019-07-07 12:18:47
Revision:15221
Relative:URL: ^/trunk

Last errors/warnings:
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
- W: java.io.IOException: Attribution is not loaded yet
- W: Bing: attribution data is not yet loaded.
}}}
"	defect	closed	normal		Core	latest	duplicate	template_report relation route sort dual-way