Bug 40701 - Add optional description to a policy
Add optional description to a policy
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Policies
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-16 22:20 CET by Michael Grandjean
Modified: 2019-01-03 07:19 CET (History)
2 users (show)

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?: 2: Will only affect a few 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.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): External feedback
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2016-02-16 22:20:26 CET
It should be possible to add a description to a policy.
Especially in larger environments, this would help a lot to maintain policies and to explain what they are good for and why they were added in the first place.
Comment 1 Florian Best univentionstaff 2016-11-05 00:15:07 CET
This requires the schema of univentionPolicy to allow the description attribute and a simple UDM property at all policy modules.
Comment 2 Florian Best univentionstaff 2017-06-28 14:53:09 CEST
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:19:59 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.