View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006505 | Taler | wallet-core | public | 2020-08-21 15:50 | 2026-09-19 14:45 |
| Reporter | Florian Dold | Assigned To | Florian Dold | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | text | Reproducibility | have not tried |
| Status | closed | Resolution | won't fix | ||
| Target Version | 1.6 | Fixed in Version | 1.6 | ||
| Summary | 0006505: define UX and API for "global errors/notifications" | ||||
| Description | Global errors/notifications are events that need user attention and/or that aren't displayed in a transaction list item. Examples: * backup/sync failed (with >N retries) * money lost due to recoup * (Should this be a transaction instead?! => it could *also* be a transaction) * refresh (after pay) fails for too long * (Should maybe also be a transaction? => no) * Exchange master public key changes, so refresh becomes impossible unless the new public key is audited or directly trusted/accepted. * Wallet DB state inconsistencies that indicate some bug / corruption To prevent spammy notifications / thrashing, every global error/notification should get some ID based on the type of the problem and the underlying resource. | ||||
| Tags | No tags attached. | ||||
| Is this the same as WebEx pending operations? They are shown as a header on the top of the wallet popup. It is designed to hold up to 3 elements of any type and clicking them will lead you to the pending transaction (or maybe the screen to solve the problem / find more information). I'm worried that 3 elements may not be enough. | |
| I think the answer is "it depends". For refreshes, I can see that we can integrate them into the pending transactions. However, for stuff like "your backup isn't working", this is not really a transaction. It doesn't have a currency and amount associated with it. But it should probably be rendered "in the vicinity" of where we show pending transactions. Or maybe even more prominently? I'm not sure! | |
| I don't think this is required anymore with the current wallet-core design that's based around resources (exchange entries, transactions, bank accounts) with their own life cycle. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-08-21 15:50 | Florian Dold | New Issue | |
| 2020-08-21 15:50 | Florian Dold | Status | new => assigned |
| 2020-08-21 15:50 | Florian Dold | Assigned To | => Florian Dold |
| 2020-09-11 20:56 | Christian Grothoff | Severity | minor => text |
| 2021-06-14 15:28 | Florian Dold | Description Updated | |
| 2021-06-14 15:31 | Florian Dold | Description Updated | |
| 2021-06-15 08:54 | Florian Dold | Description Updated | |
| 2022-09-23 18:56 | sebasjm | Note Added: 0019178 | |
| 2022-09-27 17:23 | Florian Dold | Note Added: 0019192 | |
| 2023-04-04 14:19 | Florian Dold | Target Version | => post-1.0 |
| 2023-04-13 18:36 | Florian Dold | Category | wallet (TS core) => wallet-core |
| 2023-08-24 14:24 | Florian Dold | Assigned To | Florian Dold => |
| 2023-08-24 14:24 | Florian Dold | Status | assigned => acknowledged |
| 2026-07-28 20:42 | Florian Dold | Assigned To | => Florian Dold |
| 2026-07-28 20:42 | Florian Dold | Status | acknowledged => closed |
| 2026-07-28 20:42 | Florian Dold | Resolution | open => won't fix |
| 2026-07-28 20:42 | Florian Dold | Note Added: 0029288 | |
| 2026-09-19 14:45 | Christian Grothoff | Fixed in Version | => 1.6 |
| 2026-09-19 14:45 | Christian Grothoff | Target Version | post-1.0 => 1.6 |