View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006381 | Taler | libeufin-nexus | public | 2020-06-14 17:19 | 2023-04-17 13:18 |
| Reporter | Florian Dold | Assigned To | |||
| Priority | low | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Target Version | 0.9.5 | ||||
| Summary | 0006381: implement and test transaction identification matching for INFO->PENDING->BOOKED transition | ||||
| Description | Currently we don't support a transaction transitioning between these states. In order to do this, a transaction should be marked with a foreign key column "supersededBy" that points to the newer "version" of the same transaction with a different status. By default, the superseded transaction shouldn't be returned in the transactions list anymore. The superseded and current transaction must share some common transaction identifier. | ||||
| Tags | No tags attached. | ||||
|
|
If one transaction gets from PENDING to BOOKED (becoming therefore superseded), then this bug suggests that such transaction shows up in the list only as long as is pending. Then, once it gets superseded by the new booked status, it won't show anymore? If yes, why would the booked status NOT be interesting? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-06-14 17:19 | Florian Dold | New Issue | |
| 2020-11-10 11:57 | MS | Target Version | => 0.9.2 |
| 2021-01-14 00:26 | Florian Dold | Description Updated | |
| 2023-01-08 11:19 | Christian Grothoff | Target Version | 0.9.2 => 0.9.3 |
| 2023-04-11 10:54 | MS | Note Added: 0020062 | |
| 2023-04-11 10:54 | MS | Priority | normal => low |
| 2023-04-13 20:26 | Florian Dold | Project | libeufin => Taler |
| 2023-04-13 21:50 | Florian Dold | Category | other => libeufin-nexus |
| 2023-04-17 13:18 | Florian Dold | Target Version | 0.9.3 => 0.9.5 |
