Bug 40098 - Exam buttons/info does not appear after automatic redirection to computer room module
Exam buttons/info does not appear after automatic redirection to computer roo...
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Computer room
UCS@school 4.1
Other Linux
: P5 normal (vote)
: UCS@school 4.1.x
Assigned To: UCS@school maintainers
:
Depends on:
Blocks: 44157
  Show dependency treegraph
 
Reported: 2015-11-25 09:36 CET by Valentin Heidelberger
Modified: 2019-02-05 21:15 CET (History)
2 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 Valentin Heidelberger univentionstaff 2015-11-25 09:36:48 CET
After the exam creation wizard is completed, the user is being redirected to the computer room module, where the remaining exam time and buttons to end the exam should be. But any info/buttons regarding the current exam appears only if the user reloads/reopens the module once after the redirection.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2016-01-17 23:53:15 CET
I'm unable to reproduce this problem. Can you give any further information or does the problematic system still exist/is is reproducible?
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:15:38 CET
This issue has been filled against UCS@school 4.1 (R2). The maintenance with bug 
and security fixes for UCS@school 4.1 (R2) has ended on 5th of April 2018.

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