Bug 36765 – concurrent selecting of room

Bug 36765 - concurrent selecting of room


Summary:	concurrent selecting of room

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Computer room
Version:	UCS@school 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS@school 4.0.x
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-17 17:32 CET by Florian Best
Modified:	2019-02-05 21:20 CET (History)
CC List:	2 users (show)

See Also:	34602
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
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 Florian Best

2014-11-17 17:32:45 CET

If 2 users have the 'select room' dialog opened and are acquiring a room the second user will not receive the hint that he overtakes a session from another teacher.

Comment 1 Sönke Schwardt-Krummrich

2014-11-17 20:30:23 CET

This seems to be a regression.

Comment 2 Florian Best

2014-11-17 20:39:13 CET

(In reply to Sönke Schwardt-Krummrich from comment #1)
> This seems to be a regression.
No.

We would have to do a 2nd request immediately before selecting the room to fix it.

Comment 3 Sönke Schwardt-Krummrich

2019-02-05 21:20:32 CET

This issue has been filled against UCS@school 4.0. The maintenance with bug 
and security fixes for UCS@school 4.0 has ended on May 31, 2016.

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