Bug 33459 - ucsschool/exam/default/room not evaluated
ucsschool/exam/default/room not evaluated
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Exam mode
UCS@school 3.2
Other Linux
: P5 normal (vote)
: UCS@school 3.2.x
Assigned To: UCS@school maintainers
:
Depends on:
Blocks: 44157
  Show dependency treegraph
 
Reported: 2013-11-18 16:15 CET by Florian Best
Modified: 2019-02-05 21:25 CET (History)
3 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2013-11-18 16:15:16 CET
The UCRV ucsschool/exam/default/room is not evaluated so that the room is not preselected when creating a exam.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2013-12-03 21:32:14 CET
Which value of ucsschool/exam/default/room has been used for the test?
Comment 2 Florian Best univentionstaff 2013-12-04 08:04:29 CET
raum3
Comment 3 Florian Best univentionstaff 2016-06-15 22:05:04 CEST
Maybe it has to be a DN?
Comment 4 Jan Christoph Ebersbach univentionstaff 2016-11-21 15:11:09 CET
A customer reported that in general the computer room isn't pre-selected in the exam module compared to the behaviour of the computer room module.
Comment 5 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:25:57 CET
This issue has been filled against UCS@school 3.2. The maintenance with
bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
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.