View Issue Details

IDProjectCategoryView StatusLast Update
0009615Talermerchant backendpublic2026-09-19 14:40
ReporterDana Dram Assigned ToFlorian Dold Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeveritytweakReproducibilityalways
Status informingResolutionfixed 
Product Versiongit (master) 
Target Version1.6Fixed in Version1.6 
Summary0009615: Auto-Generate IDs for forms
DescriptionCurrently, almost all forms in the application include an ID field that must adhere to specific rules. These rules often require users to manually input IDs with a large number of characters, which can be time-consuming, error-prone, and frustrating. The proposed feature aims to enhance usability by enabling the system to automatically generate these IDs based on predefined rules. By automating this process, users will no longer need to manually create or input IDs, reducing errors and saving time.
TagsNo tags attached.
Attached Files
Id1.png (49,282 bytes)   
Id1.png (49,282 bytes)   
ID2.png (30,265 bytes)   
ID2.png (30,265 bytes)   
ID3.png (21,835 bytes)   
ID3.png (21,835 bytes)   

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2025-03-12 23:26

manager   ~0024188

The 'wire transfer ID' actually clearly must be a reserve public key, so the label is wrong there and needs to be fixed. That one we cannot auto-generate as it must match the reserve private key. That said, I'm not sure *where* you found that form.

As for the others, the IDs are supposed to help the user re-identify the added object and serve to document for the users what their accounts/devices/templates are by assigning them memorable (!) identifiers. Now, what I guess we could do for the OTP-device is to swap the input order (description, then ID) and if ID is empty default it to say the longest word legal for an ID from the description (and first if two are equally long). This could probably also be done with the product ID. This would, however, not work for the webhook, as there we don't even have a description field.

Overall, I think given what the user is configuring here, I'm not sure even that is worth doing -- none of these are things we'd expect a user to do often.

Florian Dold

2026-08-29 16:47

manager   ~0029756

In the new merchant portal webui, we are doing this. Machine identifiers are derived from the human-readable name, but can be changed in extended settings.

Issue History

Date ModifiedUsernameFieldChange
2025-03-12 15:39Dana DramNew Issue
2025-03-12 15:39Dana DramStatusnew => assigned
2025-03-12 15:39Dana DramAssigned To => Christian Grothoff
2025-03-12 15:39Dana DramFile Added: Id1.png
2025-03-12 15:39Dana DramFile Added: ID2.png
2025-03-12 15:39Dana DramFile Added: ID3.png
2025-03-12 23:26Christian GrothoffNote Added: 0024188
2025-03-12 23:27Christian GrothoffSeverityminor => tweak
2025-03-12 23:27Christian GrothoffProduct Version => git (master)
2025-03-13 13:22Christian GrothoffAssigned ToChristian Grothoff =>
2025-03-13 13:22Christian GrothoffStatusassigned => acknowledged
2025-03-13 13:22Christian GrothoffTarget Version => post-1.0
2025-03-22 13:09Christian GrothoffCategorymechant backend => merchant backend
2025-10-23 10:50Christian GrothoffTarget Versionpost-1.0 => post-2.0
2026-08-29 16:47Florian DoldAssigned To => Florian Dold
2026-08-29 16:47Florian DoldStatusacknowledged => informing
2026-08-29 16:47Florian DoldResolutionopen => fixed
2026-08-29 16:47Florian DoldNote Added: 0029756
2026-09-19 14:38Christian GrothoffTarget Versionpost-2.0 => 1.6
2026-09-19 14:40Christian GrothoffFixed in Version => 1.6