View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009676 | Taler | exchange AML backoffice (SPA) | public | 2025-03-30 10:02 | 2025-05-10 04:11 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | ||
| Priority | normal | Severity | feature | 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 | 0009676: Require explicit confirmation before MROS events | ||||
| Description | When the AML SPA is about to emit events MROS_REPORTED_SUSPICION_SUBSTANTIATED or MROS_REPORTED_SUSPICION_SIMPLE there should be an explicit confirmation check that pops up when the officer hits the "submit" button asking them to confirm that they did report the case to MROS. This is just to make sure that we didn't in our automatic event-emission logic assume MROS was submitted, but some AML officer had a different interpretation ;-). This shouldn't affect anything server-side, it's just a UI/UX tweak to double-check that this external process really happened. | ||||
| Tags | compliance, ux | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-30 10:02 | Christian Grothoff | New Issue | |
| 2025-03-30 10:02 | Christian Grothoff | Status | new => assigned |
| 2025-03-30 10:02 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-04-17 22:13 | Christian Grothoff | Tag Attached: compliance | |
| 2025-04-17 22:13 | Christian Grothoff | Tag Attached: ux | |
| 2025-05-01 20:37 | sebasjm | Status | assigned => resolved |
| 2025-05-01 20:37 | sebasjm | Resolution | open => fixed |
| 2025-05-01 20:37 | sebasjm | Note Added: 0024742 | |
| 2025-05-02 20:18 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2025-05-02 20:18 | Christian Grothoff | Target Version | 1.0 stretch goals => 1.0 |
| 2025-05-10 04:11 | Christian Grothoff | Status | resolved => closed |
