Modify

Opened 4 years ago

Last modified 3 months ago

#2557 new enhancement

Prefill bug report form instead of clipboard usage

Reported by: Chriki Owned by: team
Priority: major Component: Core
Version: latest Keywords: bug report
Cc:

Description (last modified by skyper)

I find it potentially problematic that JOSM automatically copies error reports to the clipboard. This can easily overwrite important user data which has been in the clipboard previously. I’d suggest to rather offer a button like “Copy Report to Clipboard” so that the user has the possibility to save her clipboard data before going and reporting the error here.

Thanks,
Chriki™

Attachments (0)

Change History (6)

comment:1 follow-up: Changed 4 years ago by stoecker

  • Resolution set to wontfix
  • Status changed from new to closed

Errors are seldom and in an error situation it must be easy for users to report or they don't do it.

comment:2 in reply to: ↑ 1 Changed 4 years ago by Chriki

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Replying to stoecker:

Errors are seldom and in an error situation it must be easy for users to report or they don't do it.

I agree, therefore I have suggested to add a “Copy Error Report to Clipboard” button.

I am reopening this ticket as there has been no comment, yet, on the actual (data) security problem I have mentioned: IMHO a program should not unexpectedly overwrite the contents of the system clipboard. The loss of data for the user is potentially much more severe than a not reported JOSM problem.

comment:3 Changed 4 years ago by stoecker

  • Status changed from reopened to new
  • Summary changed from Upon Errors: Don’t Automatically Copy Error Report to Clipboard to Prefill bug report form instead of clipboard usage
  • Type changed from defect to enhancement

You are right, that the clipboard loss is a drawback, but one has to choose between different possibilities. Getting the bug reports outweights the clipboard loss ATM and getting the full bug reports is an important issue.

As said these troubles are very seldom (most problems do not issue an exceptions anymore). Currently after the API 0.6 switch the number of these reports is a bit higher, but JOSM generally is very stable.

Adding another inbetween step (even a button) will reduce helpful reports.

I change that to an enhancement. When the bug-report call uses prefilled data we can drop the clipboard usage at all

comment:4 Changed 4 years ago by xeen

Ideally JOSM would open a browser page with the bug report already filled in. How about writing a bug report.html in the temp directory and opening it automatically in the default browser? It even reduces the amount of steps to take.

I haven't checked, but I believe submitting to another domain from a local file is going make the browsers post a dozen warnings which isn't too good either.

comment:5 Changed 3 months ago by skyper

  • Keywords reportbug added

comment:6 Changed 3 months ago by skyper

  • Description modified (diff)
  • Keywords bug report added; reportbug removed

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team. Next status will be 'new'.
Next status will be 'needinfo'.The owner will change to Chriki
as duplicate The resolution will be set to duplicate. Next status will be 'closed'.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous. Next status will be 'assigned'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.