View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010630 | Taler | deployment and operations | public | 2025-11-18 18:18 | 2025-11-28 18:45 |
| Reporter | vecirex | Assigned To | vecirex | ||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 1.0 | ||||
| Target Version | post-1.0 | ||||
| Summary | 0010630: Set my.taler-ops.ch live | ||||
| Description | This ticket initially was just thought as a meta / reminder ticket for my personal use, but started to be seen as an actual ticket to solve; the open description text combined with this ticket having many relations (some already solved) added to the confusion: for developers it was unclear as what to do / how to achieve the desired state of starting the beta phase useful for and with real customers. Severe errors were already solved, other might emerge. In any case, every task goes in an own ticket, which has to be solved as to set my.taler-ops.ch live, this also includes the necessary steps to set it live; that is, all tickets will be added as a relation to this ticket which block it being closed (relation type: depends on). Such tickets can also be tickets indicating that a specific area of the system needs more testing, but this must be concrete and not that open as it was before with just a bullet point in the description text where it looks like work will never be concluded. Done like this, it's also legitimate that such a ticket blocks my.taler-ops.ch to go live, and people can also see and ask what's the situation with that testing blocking this ticket. Nice-to-have issues, like missing translations in remote corners of the backend, should be removed from this ticket as to not block it being solvable anytime soon. We could collect them in another ticket (if even needed) to have necessary steps also collected which we need to undertake to make the taler-merchant more mature to a further level -- however, such a level must properly be defined and made achievable (e.g., full translation to German of taler-merchant in all its strings), otherwise the ticket can never be closed. This is to avoid that we never put it my.taler-ops.ch online for minor issues that are not yet solved and which can be explained as such to interested merchants and also the public, including to the press. | ||||
| Tags | No tags attached. | ||||
| related to | 0010545 | confirmed | Christian Grothoff | Taler | add error code in merchant spec [30d] |
| related to | 0010546 | confirmed | Christian Grothoff | Taler | merchant backend should report the status of each exchange for each bank account [3d] |
| related to | 0010581 | closed | sebasjm | Taler | Profiles to simplify merchant backend |
| related to | 0010593 | resolved | sebasjm | Taler | Taler Merchant Backend SPA: Delete screen "Wire transfer" and apply po file generation for i18n |
| related to | 0010626 | confirmed | sebasjm | Taler | Version string mismatch frontend <-> backend: intentional? |
| related to | 0010627 | confirmed | Taler | For exchanges w/ KYC: taler-merchant-kyccheck and "KYC Status" in the UI can be brought out of touch; leading to various issues | |
| related to | 0010257 | confirmed | Taler | taler-merchant-demos README is very outdated | |
| related to | 0010172 | resolved | Christian Grothoff | Taler | should not be able to create to create tokens with a token |
| related to | 0010624 | closed | Christian Grothoff | Taler | For exchanges w/ KYC: taler-merchant-kyccheck must run (explicit context to mention: TOPS/CHF) |
| parent of | 0010631 | closed | Christian Grothoff | Taler | TOPS/CHF payment leads to core dump in newest taler-merchant-httpd |
| parent of | 0010649 | resolved | sebasjm | Taler | Merchant Backend: Templates do not get updated and the clear button is dysfunctional |
| parent of | 0010682 | resolved | Bohdan | Taler | Within specific versions, merchant can be not upgraded automatically (from v1.1.0 or earlier to 1.2.0+) |
| parent of | 0010683 | assigned | Stefan | Taler | Test template functionality in taler-merchant v1.2.2 and higher |
| parent of | 0010684 | assigned | vecirex | Taler | Test if refund of orders, partial and full, also work with iOS; for Android, test more cases |
| parent of | 0010685 | assigned | vecirex | Taler | Check if taler-merchant's financial records for a given instance are understandable / sum up correctly |
| parent of | 0010689 | assigned | vecirex | Taler | Test if settlements work, also testing changing delays |
| related to | 0010633 | confirmed | Taler | Creating an order in newest taler-merchant (v1.2.0) has no easy mode anymore | |
| related to | 0010410 | assigned | Stefan | Taler | qc: balance limit, with second transfer going over limit |
| Not all the children of this issue are yet resolved or closed. | |||||
|
|
make title more precise |
|
|
Nice ticket, let me recommend to do the select for "merchant" in https://bugs.gnunet.org/view_all_bug_page.php to see all bug tickets concerning the Merchant Backend. Consequently, I picked some of them which sound relevant to get prioritised and added those as related to this ticket. |
|
|
0010625 can be closed as it seems |
|
|
Title & descr of this ticket changed, as to make this ticket useful for others, not just for me. Note to me was this, and this being part of the descr text created confusion as what is blocking my.taler-ops.ch to go online: - i18n-related observations tickets (wrong translations, bad defaults for TOPS/CHF, missing translations etc.) - confusing warnings when not running the taler-merchant for self-provisioning - confusion with login id / instance; can lead to rabbit holes for others, as it did for me - podman image for very quick tests resusing running config for TOPS/CHF; with and without systemd - UX issues like time between KYC completed and account usable; suggestion for button - documentation tickets for all things which cannot be fixed quickly; describe possible work arounds - troubleshooting documentation to avoid losing time again in the future (and save time for other operators, too) Also to do: - Scroll through recent chats to find issues not mentioned above; reuse text / work already done from there. |
|
|
Severity is not trivial anymore (as just a mere -- and personal -- todo list), it's now a feature request |
|
|
Make descr text more precise as what to do with other tickets which are related to this ticket, but don't belong here: to be coordinated with @stefan at a call late in the evening today. |
|
|
As a first example of how this ticket shall work: Added blocker ticket 0010682, as v1.2.2 of the taler-merchant contains the needed fix 0010649, so that interested merchants are able to create template payments which actually work, but upgrade to this newest version doesn't work (yet). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-18 18:18 | vecirex | New Issue | |
| 2025-11-18 18:18 | vecirex | Status | new => assigned |
| 2025-11-18 18:18 | vecirex | Assigned To | => vecirex |
| 2025-11-18 18:19 | vecirex | Description Updated | |
| 2025-11-18 18:22 | vecirex | Summary | Meta/Reminder ticket for merchant-related issues / tickets not yet opened (special context: TOPS/CHF) => Meta/Reminder ticket for merchant-related issues / tickets not yet opened (not limited to, but focusfi context: TOPS/CHF) |
| 2025-11-18 18:22 | vecirex | Note Added: 0026532 | |
| 2025-11-18 18:23 | vecirex | Summary | Meta/Reminder ticket for merchant-related issues / tickets not yet opened (not limited to, but focusfi context: TOPS/CHF) => Meta/Reminder ticket for merchant-related issues / tickets not yet opened (not limited to, but focus context: TOPS/CHF) |
| 2025-11-18 19:28 | Christian Grothoff | Product Version | 1.2 => 1.0 |
| 2025-11-18 19:28 | Christian Grothoff | Target Version | 1.2 => post-1.0 |
| 2025-11-18 21:29 | Stefan | Note Added: 0026536 | |
| 2025-11-18 21:31 | Stefan | Relationship added | related to 0010545 |
| 2025-11-18 21:31 | Stefan | Relationship added | related to 0010546 |
| 2025-11-18 21:42 | Stefan | Relationship added | related to 0010581 |
| 2025-11-18 21:42 | Stefan | Relationship added | related to 0010593 |
| 2025-11-18 21:42 | Stefan | Relationship added | related to 0010625 |
| 2025-11-18 21:42 | Stefan | Note Added: 0026537 | |
| 2025-11-18 21:44 | Stefan | Relationship added | related to 0010626 |
| 2025-11-18 21:59 | Stefan | Relationship added | related to 0010280 |
| 2025-11-18 22:01 | Stefan | Relationship added | related to 0010627 |
| 2025-11-18 22:03 | Stefan | Relationship added | related to 0010257 |
| 2025-11-18 22:05 | Stefan | Relationship added | related to 0010172 |
| 2025-11-18 22:39 | Stefan | Relationship added | related to 0010624 |
| 2025-11-19 12:30 | Stefan | Relationship added | related to 0010631 |
| 2025-11-21 11:29 | Stefan | Relationship added | related to 0010633 |
| 2025-11-25 10:44 | Stefan | Relationship added | related to 0010649 |
| 2025-11-28 10:22 | Stefan | Relationship added | related to 0010410 |
| 2025-11-28 16:25 | vecirex | Category | other => deployment and operations |
| 2025-11-28 16:25 | vecirex | Summary | Meta/Reminder ticket for merchant-related issues / tickets not yet opened (not limited to, but focus context: TOPS/CHF) => Set my.taler-ops.ch live |
| 2025-11-28 16:25 | vecirex | Description Updated | |
| 2025-11-28 16:25 | vecirex | Note Added: 0026662 | |
| 2025-11-28 16:26 | vecirex | Severity | trivial => feature |
| 2025-11-28 16:26 | vecirex | Note Added: 0026663 | |
| 2025-11-28 16:31 | vecirex | Description Updated | |
| 2025-11-28 16:35 | vecirex | Description Updated | |
| 2025-11-28 16:39 | vecirex | Description Updated | |
| 2025-11-28 16:39 | vecirex | Note Added: 0026664 | |
| 2025-11-28 16:40 | vecirex | Relationship deleted | related to 0010625 |
| 2025-11-28 16:41 | vecirex | Relationship added | parent of 0010682 |
| 2025-11-28 16:46 | vecirex | Note Added: 0026665 | |
| 2025-11-28 16:47 | vecirex | Note Edited: 0026662 | |
| 2025-11-28 16:48 | vecirex | Relationship replaced | parent of 0010631 |
| 2025-11-28 16:56 | vecirex | Relationship added | parent of 0010683 |
| 2025-11-28 17:06 | vecirex | Relationship added | parent of 0010684 |
| 2025-11-28 17:22 | vecirex | Relationship added | parent of 0010685 |
| 2025-11-28 18:19 | vecirex | Relationship added | parent of 0010689 |
| 2025-11-28 18:22 | vecirex | Note Edited: 0026664 | |
| 2025-11-28 18:44 | vecirex | Relationship deleted | related to 0010280 |
| 2025-11-28 18:45 | vecirex | Relationship replaced | parent of 0010649 |
