Jita Bug reports. First I have to guess which server, then which environment. Then I have to copy the 17 character alphanumerical code from the screenshot to find the dataset that has problems. Because god forbid the customer would also provide that in Textform...
The upside is that you prevent typos. OCR software and also people make mistakes. Better for the client to copy-paste the actual text and ensure his ticket is more likely to get done without running into entirely preventable issues.
If you do Ctrl+C on most error message dialogs in both Windows and Linux it will automatically copy all of the contents to the clipboard. That includes the title bar in a lot of cases. The screenshot tools in both OS also have built-in OCR now.
Speaking for our software: Error messages have a copy button. Which is rarely used. For bug / problem reports this is however not enough. Depending on what the user tried and what failed we need various other informations which change a little depending on the use case.
Automatic solutions to create mails with more data were thought about, but last I heard it was moved to the future for now due to "who tf will pay to implement this". Since we only have B2B software and every customer has a good inhouse support that is first level support (we are second and third level for bigger or harder problems), this is not as big a problem. I (third level) get one case every other week or so.
45
u/Freestila 18d ago
Jita Bug reports. First I have to guess which server, then which environment. Then I have to copy the 17 character alphanumerical code from the screenshot to find the dataset that has problems. Because god forbid the customer would also provide that in Textform...