View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009967 | Taler | specification | public | 2025-05-15 16:57 | 2025-05-15 21:57 |
| Reporter | sebasjm | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | acknowledged | Resolution | open | ||
| Target Version | post-2.0 | ||||
| Summary | 0009967: we need a reporting endpoint for http services | ||||
| Description | For any service like bank/exchange/merchant/challenger/... the user may encounter problems and would like to easy report the issue. Today it needs to have a mantis user and know how to proceed. Which is good enough but leaves some issues without report which we would like to know to fix it. On the other hand, the same software will be served by third party (like netzbon, gls) and users of that service may not encounter mantis so friendly. Additionally, some bugs may be related to the system administration which the sysadmin would not report (reporting here will be a waste of time) use asking all users to report on this issue tracking is not the best proposal. ---- Given the above, we should have an endpoint on every service so client software of that web service could report problems (automatically or manually) Automatic report could be: slow responses, unexpected responses, client side errors related to the service (in the case of SPA this is clear but in the case of wallet this may not apply) Manual reports: this could be an easy way to send a screenshot of something that doesn't work as expected due to a bug or misconfiguration. The endpoint receiving this report should save a queue which the sysadmin could then check status, decide if there is something to report here on mantis or maybe even download the source code, fix it and share the patch :) We should create a spec for this first: * server side endpoint * payload definition of the report (how much information do we send?) * client side UI (how does the user find that a report can be sent) * what is a good definition of an error that should be automatically reported (if the user allows that) We may also link here some other implementations | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-15 16:57 | sebasjm | New Issue | |
| 2025-05-15 21:57 | Christian Grothoff | Status | new => acknowledged |
| 2025-05-15 21:57 | Christian Grothoff | Target Version | => post-2.0 |
