View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009678 | Taler | exchange AML backoffice (SPA) | public | 2025-03-30 10:42 | 2025-05-10 04:13 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | ||
| Priority | normal | Severity | text | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.0 | Fixed in Version | 1.0 | ||
| Summary | 0009678: create GANA registry for properties | ||||
| Description | We have one for KYC attributes, but should also create a registry for the properties. We probably have generic properties we always use, and then deployment-specific properties (TOPS, GLS). So each property should have: 1) unique name 2) associated deployment or 'generic' 3) type 4) description | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-30 10:42 | Christian Grothoff | New Issue | |
| 2025-03-30 10:42 | Christian Grothoff | Status | new => assigned |
| 2025-03-30 10:42 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-04-17 23:40 | Christian Grothoff | Assigned To | sebasjm => |
| 2025-04-17 23:40 | Christian Grothoff | Status | assigned => confirmed |
| 2025-04-23 19:10 | sebasjm | Assigned To | => sebasjm |
| 2025-04-23 19:10 | sebasjm | Status | confirmed => assigned |
| 2025-04-23 19:11 | sebasjm | Target Version | post-1.0 => 1.0 |
| 2025-04-23 21:47 | sebasjm | Status | assigned => resolved |
| 2025-04-23 21:47 | sebasjm | Resolution | open => fixed |
| 2025-05-10 04:12 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2025-05-10 04:13 | Christian Grothoff | Status | resolved => closed |
