| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009738 | Taler | exchange AML officer webui | public | 2025-04-15 14:51 | 2025-05-10 02:11 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | 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 | major | Reproducibility | always |
| 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 | 0009738: AML SPA allows multi-select for expiration measures | ||||
| Description | ... but we can only have ONE expiration measure (measure to be taken upon expiration). Note that we usually call it the "successor measure" in the code, so might be good to call the field "successor measure" as well (tooltip / hint could be used to clarify that it is the "measure taken automatically upon expiration of the current decision". Anyway, the main bug is that there can only be one expiration/successor measure, and thus the SPA must not allow entering multiple. Plus, if it does, things are likely to break in "interesting" ways with the backend... | ||||
| Tags | No tags attached. | ||||
- Anonymous