View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007865 | Taler | wallet-core | public | 2023-06-19 08:42 | 2023-06-26 10:58 |
| 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 | duplicate | ||
| Target Version | 0.9.3 | ||||
| Summary | 0007865: consider having a history for some transactions | ||||
| Description | Some transactions can have a more complex history, such as a payment where we re-select a coin after we find out it has been already spent. The wallet currently does this destructively, and there is no way to find out the history of what happened and where money potentially was lost. Thus, for some transactions it would make sense to record some more history data. | ||||
| Tags | No tags attached. | ||||
| duplicate of | 0007866 | acknowledged | transactions should keep some history data |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-06-19 08:42 | Florian Dold | New Issue | |
| 2023-06-19 08:42 | Florian Dold | Status | new => assigned |
| 2023-06-19 08:42 | Florian Dold | Assigned To | => Florian Dold |
| 2023-06-19 11:29 | sebasjm | Relationship added | related to 0007866 |
| 2023-06-26 09:26 | Florian Dold | Status | assigned => closed |
| 2023-06-26 09:26 | Florian Dold | Resolution | open => duplicate |
| 2023-06-26 09:26 | Florian Dold | Relationship replaced | duplicate of 0007866 |
| 2023-06-26 10:58 | Florian Dold | Target Version | post-1.0 => 0.9.3 |