Just to clarify.
You have write access to the shared calender and want to add another event, while there is already one in that same shared calendar?
Or do you want to add an event to another calendar while there is an event in a shared one?

The former. I have the write access to the shared calendar and want to add an event in a time slot that another event of the same calendar already covered a part or the whole.

Why there is no fix in recent updates?!

Happening here also.

I have upgraded recently from 3.1.4 version into 3.2.0

3.1.4 version showed conflict message, but allowed us to create the event anyway.

Today, I've downgraded my setup into 3.1.4 version.

As stated on my previous comment, conflict messages are shown, but SOGo still allowing me to create the event.

Is this helpful on any way?

In my case, SOGo does not allow to create any event which has conflict in a shared calendar!
I am still waiting for the fix in the next updates...

On my understanding, this is clearly a regression introduced on 3.1.5 (which I didn't tested) or 3.2.0 (which is failing you and has been failing me for a couple of days)

I'll try to test 3.1.5 and see if I can narrow things a bit.

Conflicts are only handled for resources, so you're trying to invite a resource that has reach its maximum simultaneous bookings limit.

The error displayed in the Web interface has been fixed a few days ago.

Many thanks for the answer Francis.

FWIW, I am not using resources. What I do is:

Create an event on my calendar and invite a user who has appointments already created on this day and time frame.

As I said, on 3.1.4 conflicts are shown, but I can save the task anyway. On 3.2.0, I cannot do such thing.

So, should I expect this to be fixed on the 3.2.1 release? Is there any place I can check the release status and/or release dates?

Many thanks for the answer and the outstanding developing sogo

Try the latest nightly build. It has been fixed.

Indeed it is fixed on the nightly build. Thanks!

So, I guess this fix is going to be included on 3.2.1, am I right? Is there any candidate date or so?

Again, many many thanks.

Thank you,
finally it was solved. Now I get a warning message when there is a conflict between events in a shared calendar, and then I'm able to save the second event too.
I can confirm it as resolved.

https://github.com/inverse-inc/sogo/commit/5208e46d100612bff2eb3933db9d7428ae6a9b53