Bug 31521 - No warning when exam is finished and project file does not exist
No warning when exam is finished and project file does not exist
Status: CLOSED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Exam mode
UCS@school 4.1 R2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-27 18:00 CEST by Alexander Kläser
Modified: 2023-06-12 15:39 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very 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.034
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

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2013-05-27 18:00:13 CEST
Currently, an exam can be finished even though the project file has been deleted. It is important to be able to finish the exam in any case, however at least a warning would be important to prompt to the teacher.
Comment 1 Alexander Kläser univentionstaff 2013-05-27 18:00:47 CEST
See also Bug 31158, Comment 23 for more background information.
Comment 2 Florian Best univentionstaff 2016-12-12 10:17:47 CET
This causes e.g. Bug #43168
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:43:10 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.