id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
14569	Replace geometry: remember tag conflict resolution for next items	bagage	team	"==== What steps will reproduce the problem?
1. Use the conflation plugin to conflate(!) things between 2 datasets
2. Have a conflict on all items between the 2 datasets
3. Conflate all items

==== What is the expected result?

First you handle manually the conflict for the first item, then select a checkbox near it ""remember my choice for next conflicts"". Then, all next items are automatically merged for this specific issue.

Either having one checkbox per tag conflict that would automatically fix next conflicts with the exact same tag conflict OR a global checkbox that may be useful if you want to solve multiple tags conflicts at once and for all items? I personally would prefer the former but I have no strong opinion on this.

==== What happens instead?

You have to solve the conflict for every item manually. Not doable for 100+ items.

==== Please provide any additional information below. Attach a screenshot if possible.

{{{
Build-Date:2017-03-24 10:36:25
Revision:11772
Is-Local-Build:true

Identification: JOSM/1.5 (11772 SVN en) Linux Debian GNU/Linux 9.0 (stretch)
Memory Usage: 829 MB / 1760 MB (572 MB allocated, but free)
Java version: 1.8.0_121-8u121-b13-4-b13, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1920x1080
Maximum Screen Size: 1920x1080
Java package: openjdk-8-jre:amd64-8u121-b13-4
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-13
Program arguments: [${HOME}/CL096-CLERIEUX/test-small.osm]
Dataset consistency test: No problems found

Plugins:
+ PicLayer (33148)
+ conflation (0.5.1)
+ jts (32699)
+ rex (26)
+ utilsplugin2 (33182)

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.
}}}
"	enhancement	new	normal		Plugin conflation	latest		template_report conflict