Closed nus-se-bot closed 6 months ago
I feel that this would be a duplicate of #176 , where the reasoning would almost be the same, also to be more inclusive of people who may have the possibility of having a minute meeting before changing the topic Fix: To be more detailed in the definition of what meetings can do with #176. Hence I am closing this, as it overlaps with #176
Content:
In the current implementation, the application allows scheduling meetings with only a one-minute gap between them. This scenario is highly impractical in a real-world setting where back-to-back meetings typically require more time in between for preparation and context switching. Reproducing the issue: Schedule a meeting for a user at a certain time (e.g., 12/04/2024 18:00). Schedule another meeting for the same user one minute later (e.g., 12/04/2024 18:01).
Expected:
The application should prevent scheduling meetings with unrealistically short intervals, aligning with realistic scenarios of meetings requiring certain buffer times.
Actual:
The application allows scheduling meetings with only a one-minute gap.
Suggestion:
Implement a minimum time gap requirement between meetings. For example, a default buffer of 15 minutes between end and start times of consecutive meetings could be a starting point for a more realistic approach.
Labels:
severity.Medium
type.FunctionalityBug
original: Shauryan123/ped#6