View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009739 | Taler | exchange AML backoffice (SPA) | public | 2025-04-15 17:00 | 2025-04-16 16:10 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | ||
| Priority | urgent | Severity | block | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.0 | ||||
| Summary | 0009739: rules are not preserved | ||||
| Description | We had said that the rules should be by-default preserved if the user did not change anything. I'm going into the decision SPA, try to touch as little as possible, and then the summary tells me that I've defined no rules (didn't touch the rule page, indeed!) and thus the account will basically be unrestricted --- instead of *preserving* the rules we started with (and that are shown as 'never' expiring in the 'rules' page). I don't even have a button to "keep current rules" or "reset to current rules" (good after editing!). When I pick from the 3 "default" plans, I cannot easily go back to the "current" rules (button missing!). Furthermore, the limits should be different: The "Basic" plan should have: - Balance: 10000 - Transaction: 1000 - withdraw: 2500 / month - merge: 2500 / month - aggregate/deposit: 5000 / month, escalation: preserve-investigate - aggregate/deposit: 50000 / year, escalation: preserve-investigate - refund/close: no limit The "Premium" plan should have: - Balance: 10000 - Transaction: 1000 - withdraw: 2500 / month - merge: 2500 / month - aggregate/deposit: 15000 / month, escalation: preserve-investigate - aggregate/deposit: 150000 / year, escalation: preserve-investigate - refund/close: no limit | ||||
| Tags | No tags attached. | ||||
|
|
Oh, and it must be possible to set an 'expiration' for the freeze/basic/premium choices. Right now, we can ONLY set an expiration via 'add', but not for the "blue" buttons. Note that the expiration/review period must be set risk-based, so there cannot be a simple default. It is *possible* that the 'expiration' buttons are just weird, and should just not be within the "add" box (maybe above?). Also, you have "in a week, /month /year", might be good to also have a "never" button. |
|
|
> rules should be by-default preserved if the user did not change anything * new rules shown on top * current rules show at the bottom * new rules are loaded from the current rules on viewload > "reset to current rules" button * "reset rules" added which load again the current rules * "add rule form" is now initially hidden, there is abutton to "add new rule" > limits should be: the basic > limits should be: the premium * ACK > it must be possible to set an 'expiration' for the freeze/basic/premium choices > the 'expiration' buttons should just not be within the "add" box * expiration_time is now separated from the "add new rule" form * succesor measure is also now in the same form with expiration_time (it was in justification) > might be good to also have a "never" button * added never for expiration * also added "reset measure" and "reset expiration" to load from the current limits |
|
|
5b07bb1a5..cbca95c72 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-04-15 17:00 | Christian Grothoff | New Issue | |
| 2025-04-15 17:00 | Christian Grothoff | Status | new => assigned |
| 2025-04-15 17:00 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-04-15 17:06 | Christian Grothoff | Note Added: 0024559 | |
| 2025-04-16 15:59 | Christian Grothoff | Description Updated | |
| 2025-04-16 16:01 | Christian Grothoff | Description Updated | |
| 2025-04-16 16:08 | sebasjm | Note Added: 0024582 | |
| 2025-04-16 16:10 | sebasjm | Status | assigned => resolved |
| 2025-04-16 16:10 | sebasjm | Resolution | open => fixed |
| 2025-04-16 16:10 | sebasjm | Note Added: 0024583 |
