View Issue Details

IDProjectCategoryView StatusLast Update
0009615Talermechant backendpublic2025-03-13 14:22
ReporterDana Dram Assigned To 
PrioritynormalSeveritytweakReproducibilityalways
Status acknowledgedResolutionopen 
Product Versiongit (master) 
Target Versionpost-1.0 
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)   

Activities

Christian Grothoff

2025-03-13 00: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.

Issue History

Date Modified Username Field Change
2025-03-12 16:39 Dana Dram New Issue
2025-03-12 16:39 Dana Dram Status new => assigned
2025-03-12 16:39 Dana Dram Assigned To => Christian Grothoff
2025-03-12 16:39 Dana Dram File Added: Id1.png
2025-03-12 16:39 Dana Dram File Added: ID2.png
2025-03-12 16:39 Dana Dram File Added: ID3.png
2025-03-13 00:26 Christian Grothoff Note Added: 0024188
2025-03-13 00:27 Christian Grothoff Severity minor => tweak
2025-03-13 00:27 Christian Grothoff Product Version => git (master)
2025-03-13 14:22 Christian Grothoff Assigned To Christian Grothoff =>
2025-03-13 14:22 Christian Grothoff Status assigned => acknowledged
2025-03-13 14:22 Christian Grothoff Target Version => post-1.0