View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007152 | Taler | wallet (WebExtension) | public | 2022-01-20 16:14 | 2023-01-26 22:53 |
| Reporter | sebasjm | Assigned To | sebasjm | ||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.9.1 | Fixed in Version | 0.9.1 | ||
| Summary | 0007152: when there is an operational error the wallet should guide the user how to proceed | ||||
| Description | Based on the error codes from TalerErrorCode https://git.taler.net/wallet-core.git/tree/packages/taler-util/src/taler-error-codes.ts#n1766 ============================ Unexpected situations ------------------------------ (1) The withdrawal operation could not be completed because we couldn't find an exchange. (2) Your bank suggested an exchange response with an error and you don't have any trusted or auditor exchange for this currency. (3) Before trying again you can do the following: * add a default exchange for currency KUDOS * contact your bank's exchange service provider (4) Show more technical details ============================ 1.- Text defined by the operation that failed 2.- Text defined by the error code returned 3.- Text defined by (operation,error) this will make the user not to panic 4.- call to action (dropdown or link to another page) with more debug information. | ||||
| Tags | needs ux design | ||||
|
|
A bit generic for a bug report. I guess this goes with the URI-triggered error injection testing? |
|
|
I have updated the issue with more information. The target is to have one UI component that is going to be render after every operation with if the operation ended with error. |
|
|
fixed 4a781bd0dd8828ce152f6ab2c3f1bbd6b5e826f7 new UI shows title `what failed`, and the `reason` in the description. "show more" show the json with detailed information with a copy button. all handlers are validated at compile-time to have the pushAlert behavior It will be nice to have (3) but I'm marking this as solved by now. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-01-20 16:14 | sebasjm | New Issue | |
| 2022-01-20 16:14 | sebasjm | Status | new => assigned |
| 2022-01-20 16:14 | sebasjm | Assigned To | => sebasjm |
| 2022-01-20 18:14 | sebasjm | Tag Attached: needs ux design | |
| 2022-01-20 20:51 | sebasjm | Assigned To | sebasjm => belen |
| 2022-10-20 11:54 | Christian Grothoff | Assigned To | belen => |
| 2022-10-20 11:54 | Christian Grothoff | Status | assigned => acknowledged |
| 2022-10-20 11:54 | Christian Grothoff | Note Added: 0019257 | |
| 2022-11-16 18:58 | sebasjm | Description Updated | |
| 2022-11-16 18:58 | sebasjm | Assigned To | => sebasjm |
| 2022-11-16 18:58 | sebasjm | Status | acknowledged => assigned |
| 2022-11-16 19:00 | sebasjm | Note Added: 0019429 | |
| 2022-11-16 19:01 | sebasjm | Priority | normal => high |
| 2022-11-16 19:01 | sebasjm | Target Version | => 0.9.1 |
| 2022-12-20 14:26 | sebasjm | Relationship added | related to 0007329 |
| 2022-12-20 14:26 | sebasjm | Relationship added | related to 0007522 |
| 2023-01-10 00:25 | sebasjm | Note Added: 0019622 | |
| 2023-01-10 00:26 | sebasjm | Status | assigned => resolved |
| 2023-01-10 00:26 | sebasjm | Resolution | open => fixed |
| 2023-01-23 22:25 | Christian Grothoff | Fixed in Version | => 0.9.1 |
| 2023-01-26 22:53 | Christian Grothoff | Status | resolved => closed |
| 2023-04-13 20:37 | Florian Dold | Category | wallet (WebExtensions) => wallet (WebExtension) |
