Bug 57469 - Prevent app setting UCRVs from being used
Summary: Prevent app setting UCRVs from being used
Status: NEW
Alias: None
Product: UCS
Classification: Unclassified
Component: UCR
Version: UCS 5.0
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on: 52934
Blocks: 55917 57451
  Show dependency treegraph
 
Reported: 2024-07-26 10:57 CEST by Jan-Luca Kiok
Modified: 2025-06-04 08:23 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 4: Will affect most installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.091
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan-Luca Kiok univentionstaff 2024-07-26 10:57:53 CEST
For technical reasons there are UCR variables that mirror a corresponding app setting unidirectional, meaning that the only supported and working interface is the app setting and the UCRV must not be used.
From a users perspective this is rather confusing because we promote UCR as a unified configuration interface for all purposes and with explicitly providing a key we give them reason to believe that this should be working.

What we should do instead is at least make it clear when using these UCRVs that this is not the supported way of changing things and it will not work, f.e. with adapting the description or giving out a warning.
Even better would be if we would prevent these from being used, f.e. by hiding the keys from user interfaces, making them hidden technical features or by preventing them from being set by a users interaction.