template_report should attach test osm file

[simon04]

Many bugs are hard to reproduce/test when there are no test osm files attached to it. To tackle this, we could:

• ask the user to attach a test file (similar to "What is the expected result?")
• provide an automated uploading facility to attach the open layer to the ticket (after asking the user, how to deal with huge opened files?)

[bastiK]

Replying to simon04:

Many bugs are hard to reproduce/test when there are no test osm files attached to it. To tackle this, we could:

• ask the user to attach a test file (similar to "What is the expected result?")

+1

• provide an automated uploading facility to attach the open layer to the ticket (after asking the user, how to deal with huge opened files?)

We have to be careful here, because the data layer may contain private data that is not meant to be published.

[stoecker]

This request is not easy to reach. It means to deal with whole ticket interaction in josm. This is a LOT of work and I'm not sure if is really worth the effort.

[simon04]

I did not necessarily mean a change in the ticket interaction, but much more to urge the user to attach a test file in order to get the requested change realized more quickly and to help the developers.

[stoecker]

What we usually need is a OSM file containing only the relevant data. Most people would simply upload the large multi megabyte file they currently work with, without thinking about it. That does not help as well.

[Larry0ua]

file with some working and not working examples