View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009011 | Taler | wallet (Android App) | public | 2024-07-10 13:57 | 2024-07-25 22:11 |
| Reporter | Florian Dold | Assigned To | avalos | 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 | urgent | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.11 | ||||
| Target Version | 0.12 | Fixed in Version | 0.12 | ||
| Summary | 0009011: implement advanced (bank-integrated) withdrawal flow | ||||
| Description | amount selection via the wallet, netto/brutto, fee computation, and maybe even exchange selection | ||||
| Tags | No tags attached. | ||||
| The "amount" field in getWithdrawalInfoFromUri is now optional. If the amount is not provided, the user should be asked to provide the amount. Furthermore, the Android App needs to show card fees and support the suggested/max amount based on the new fields in the response. | |
| WIP in dev/ivan-avalos/withdraw2 Video: https://nextcloud.avalos.me/index.php/s/DXJC7iffYrJz3wQ | |
| Updated video: https://nextcloud.avalos.me/index.php/s/SQE4TBGKRrNbpSk There are two scenarios: 1) If there is a default amount, the user is first presented with the prompt screen. 1.1) When clicking the pencil button, the user is taken to the amount selection screen. 1.2) After entering the amount, the user is taken back to the withdraw prompt screen. 2) If there is no default amount, the user is taken directly to the amount selection screen. 2.1) After entering the amount, the user is taken back to the withdraw prompt screen. In both scenarios, the user can modify the amount as many times as they want. | |
| avalos: is this done or not? | |
| This was merged 6 days ago in commits 92bfc9302493eaa91cbc78ca9f3fb105f9632da2..56268671281dae81ebcb5b3a63dd979e732e26d8. It might still require some tweaks in the future, but it's already working. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-07-10 13:57 | Florian Dold | New Issue | |
| 2024-07-10 13:57 | Florian Dold | Status | new => assigned |
| 2024-07-10 13:57 | Florian Dold | Assigned To | => avalos |
| 2024-07-10 13:57 | Florian Dold | Issue generated from: 0008725 | |
| 2024-07-10 13:59 | Florian Dold | Note Added: 0022805 | |
| 2024-07-11 19:54 | avalos | Note Added: 0022814 | |
| 2024-07-11 19:54 | avalos | Status | assigned => implementing |
| 2024-07-16 22:39 | avalos | Note Added: 0022826 | |
| 2024-07-18 23:07 | Christian Grothoff | Note Added: 0022832 | |
| 2024-07-23 16:15 | avalos | Status | implementing => informing |
| 2024-07-23 16:15 | avalos | Resolution | open => fixed |
| 2024-07-23 16:15 | avalos | Note Added: 0022835 | |
| 2024-07-25 22:11 | Christian Grothoff | Fixed in Version | => 0.12 |
| 2024-07-25 22:11 | Christian Grothoff | Status | informing => closed |