Bug 38367 - Choice of FQDN not clear enough
Choice of FQDN not clear enough
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Setup wizard
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-04-27 09:14 CEST by Alexander Kläser
Modified: 2019-01-03 07:16 CET (History)
1 user (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?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2015042421000925
Bug group (optional): External feedback, Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2015-04-27 09:14:22 CEST
We received feedback in which the user described that he could not chose a suitable hostname. He tried "univention-01.local" which was not accepted (as the domain name was missing). Usability wise it might not be clear enough how to choose an FQDN, an additional text field or clickable question mark could be helpful at this point.

http://docs.univention.de/handbuch-4.0.html#installation:Dom%C3%A4neneinstellungen:NeueDom%C3%A4ne

[Ticket#2015042421000925]
Comment 1 Philipp Hahn univentionstaff 2017-04-19 10:35:24 CEST
See Bug #40078: Using subdomains is currently broken
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:16:25 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 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.