View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010122 | Taler | specification | public | 2025-06-23 02:46 | 2025-07-05 20:52 |
| 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 | text | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0010122: form id value should be specified in GANA | ||||
| Description | not urgent, but it will be better if we have this value in GANA so is easier to sync. I suggest to adjust the "Form:" field in GANA to the current id of the form, for example "Form: TermOfService" should change to "Form: accept-tos" For "Form: GLS_Onboarding" seems to be two implementation `gls-wallet-confirmation` and `gls-merchant-onboarding`. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-23 02:46 | sebasjm | New Issue | |
| 2025-06-29 08:22 | Christian Grothoff | Severity | minor => text |
| 2025-06-29 08:22 | Christian Grothoff | Status | new => implementing |
| 2025-07-05 20:52 | Christian Grothoff | Target Version | 1.1 => post-1.0 |