View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007866 | Taler | wallet-core | public | 2023-06-19 11:29 | 2023-08-24 14:30 |
| Reporter | sebasjm | Assigned To | 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 | always |
| Status | acknowledged | Resolution | open | ||
| Product Version | post-1.0 | ||||
| Target Version | post-1.0 | ||||
| Summary | 0007866: transactions should keep some history data | ||||
| Description | when a user see a transaction in the UI it would be nice to se the the state where the tx was and where the tx is going to be. past states: wallet core can keep a timestamp of when the tx reach that point future states: the ui can choose to show future happy path, nothing required from wallet core since it returns the graph already | ||||
| Tags | No tags attached. | ||||
| has duplicate | 0007865 | closed | Florian Dold | consider having a history for some transactions |
| From a duplicate bug report: """ 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. """ | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-06-19 11:29 | sebasjm | New Issue | |
| 2023-06-19 11:29 | sebasjm | Status | new => assigned |
| 2023-06-19 11:29 | sebasjm | Assigned To | => Florian Dold |
| 2023-06-19 11:29 | sebasjm | Relationship added | related to 0007865 |
| 2023-06-26 09:26 | Florian Dold | Note Added: 0020302 | |
| 2023-06-26 09:26 | Florian Dold | Relationship replaced | has duplicate 0007865 |
| 2023-06-26 10:45 | Florian Dold | Summary | transaction should keep some history data => transactions should keep some history data |
| 2023-08-24 14:30 | Florian Dold | Assigned To | Florian Dold => |
| 2023-08-24 14:30 | Florian Dold | Status | assigned => acknowledged |