Opened 14 years ago
Last modified 11 years ago
#6804 new enhancement
template_report should attach test osm file
Reported by: | simon04 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core bugreport | Version: | |
Keywords: | file spurious | Cc: |
Description (last modified by )
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?)
Attachments (1)
Change History (8)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
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.
comment:3 by , 14 years ago
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.
comment:4 by , 14 years ago
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.
by , 13 years ago
Attachment: | relations_sort.osm added |
---|
file with some working and not working examples
comment:5 by , 12 years ago
Keywords: | rebortbug added; template_report removed |
---|
comment:6 by , 12 years ago
Description: | modified (diff) |
---|---|
Keywords: | bug report added; rebortbug removed |
comment:7 by , 11 years ago
Component: | unspecified → Core bugreport |
---|---|
Keywords: | bug report removed |
Replying to simon04:
+1
We have to be careful here, because the data layer may contain private data that is not meant to be published.