View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003112 | SOGo | Backend General | public | 2015-02-17 14:35 | 2019-08-26 09:44 |
Reporter | rhertel | Assigned To | ludovic | ||
Priority | low | Severity | minor | Reproducibility | always |
Status | feedback | Resolution | reopened | ||
Platform | [Server] Linux | OS | Debian | OS Version | 7 (Wheezy) |
Product Version | 2.2.16 | ||||
Fixed in Version | 3.1.5 | ||||
Summary | 0003112: maximum simultaneous bookings reached too early for recurring events | ||||
Description | A resource with maximum bookings of 5 User A has a weekly repeating event for 5 times with the resource as attendee. User B tries to book the resource at the same time (weekly repeating event for 5 times) and get the warning 'Maximum number of simultaneous bookings (5) reached for resource...' For non-recurring events the resource can have 5 simultanous events. | ||||
Tags | No tags attached. | ||||
Try with the upcoming nightly builds (available in 12 hours from now) or with the upcoming v2.3.14 / v3.1.5 releases - we fixed something that can be related - reopen if necessary. |
|
It seems that this behavior is back with v4.0.7. Can anyone confirm this? |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2015-02-17 14:35 | rhertel | New Issue | |
2016-08-05 20:53 | ludovic | Note Added: 0010576 | |
2016-08-05 20:53 | ludovic | Status | new => resolved |
2016-08-05 20:53 | ludovic | Fixed in Version | => 3.1.5 |
2016-08-05 20:53 | ludovic | Resolution | open => fixed |
2016-08-05 20:53 | ludovic | Assigned To | => ludovic |
2019-08-26 09:44 | rhertel | Note Added: 0013708 | |
2019-08-26 09:44 | rhertel | Status | resolved => feedback |
2019-08-26 09:44 | rhertel | Resolution | fixed => reopened |