First Last Prev Next    This bug is not in your last search results.
Bug 26133 - Anlegen von Objekten im DHCP Modul: Container vs Superordinate
Anlegen von Objekten im DHCP Modul: Container vs Superordinate
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC - DHCP
UCS 4.1
Other Linux
: P4 normal (vote)
: UCS 4.1-3-errata
Assigned To: Florian Best
Philipp Hahn
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-02-14 10:26 CET by Andreas Büsching
Modified: 2016-11-03 11:32 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 3: Will affect average number of 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.137
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Büsching univentionstaff 2012-02-14 10:26:40 CET 
Beim Anlegen von DHCP-Objekten wird ein DropDown für Container und Superordinates angezeigt. Das ist verwirrend, da sich das Backend beim Anlegen nach dem Superordinate richtet was auch korrekt ist. Nur für das Anlegen von dhcp/service Objekten wird kein Superordinate benötigt, daher ist nur hier die Auswahl eines Containers korrekt.

Diese Vorgehensweise ist für den Benutzer denke ich unverständlich und sollte überdacht werden.
Comment 1 Florian Best univentionstaff 2016-10-13 18:38:15 CEST 
Still one of the most irritating usability issues in the DHCP/DNS modules.
Comment 2 Florian Best univentionstaff 2016-11-01 13:27:04 CET 
Simple fix: Check if a superordinate is set and remove the possible values.

univention-management-console-module-udm (6.0.11-29):
r73970 | Bug #26133: don't display container widget if no container is selectable when adding objects
r73969 | Bug #26133: don't display container widget if no container is selectable when adding objects

univention-management-console-module-udm (7.0.1-13):
r73968 | Bug #26133: don't display container widget if no container is selectable when adding objects
Comment 3 Florian Best univentionstaff 2016-11-01 13:42:01 CET 
univention-management-console-module-udm.yaml:
r73973 | YAML Bug #26133
Comment 4 Philipp Hahn univentionstaff 2016-11-02 14:24:14 CET 
OK: aptitude install '?source-package(univention-management-console-module-udm)~i'
OK: create new DNS/DHCP entries with UMC
OK: IPv4 IPv6
OK: jenkins

OK: univention-management-console-module-udm.yaml
OK: errata-announce -V --only univention-management-console-module-udm.yaml
OK: aptitude search --disable-columns -F '%p      %V      %v' '?or(?source-package(univention-management-console-module-udm),?source-package(univention-directory-manager-modules))~i'
 python-univention-directory-manager     11.0.3-43.1437.201611020126     11.0.3-43.1437.201611020126                 
 python-univention-directory-manager-cli 11.0.3-43.1437.201611020126     11.0.3-43.1437.201611020126
 univention-directory-manager-tools      11.0.3-43.1437.201611020126     11.0.3-43.1437.201611020126
 univention-management-console-module-udm        6.0.11-31.668.201611020124      6.0.11-31.668.201611020124
Comment 5 Janek Walkenhorst univentionstaff 2016-11-03 11:32:33 CET 
<http://errata.software-univention.de/ucs/4.1/321.html>
First Last Prev Next    This bug is not in your last search results.