View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006900 | Taler | wallet-core | public | 2021-06-14 10:08 | 2021-06-15 08:53 |
| 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 | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0006900: consider adding a transaction item for implicit refreshes that are failing or taking too long | ||||
| Description | The corresponding transaction item will have an amount of "0:$CURRENCY" associated with it. It only serves as a dummy to provide the following affordances: * communicating to the user that something is wrong * allowing to immediately retry * allowing to delete the transaction, which will mean that the output of the refresh it lost | ||||
| Tags | No tags attached. | ||||
| Discussed with Christian: No, this should not show up in the transaction history, but be part of the global errors/notifications. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-06-14 10:08 | Florian Dold | New Issue | |
| 2021-06-14 10:08 | Florian Dold | Status | new => assigned |
| 2021-06-14 10:08 | Florian Dold | Assigned To | => Florian Dold |
| 2021-06-15 08:53 | Florian Dold | Status | assigned => closed |
| 2021-06-15 08:53 | Florian Dold | Resolution | open => fixed |
| 2021-06-15 08:53 | Florian Dold | Note Added: 0017952 | |
| 2023-04-13 18:36 | Florian Dold | Category | wallet (TS core) => wallet-core |