Open Statspadders opened 1 year ago
The Behaviour highlighted is intended. Meetings should not start and end at the same time.
Team chose [response.Rejected
]
Reason for disagreement: The behavior is intended. There is no functionality issues here, but feature flaw.
Take for an example, the user would expect to see entries in a timetable
9:30 - 10:30 ; 10:30 - 11:30 ; 11:30 - 12:30
It would be strange for the user to enter entries such as 10:31 - 11:30, 11:31 - 12:30, or 12:31 - 13:30, as they do not accurately represent real-world conditions.
This feature flaw can cause confusion and frustration for users who may not initially understand the intended behavior. It is important to note that this flaw is not a functionality issue, but rather a design flaw that affects the usability of the system. Therefore, on second thought, I would think that this issue severity to be at least MEDIUM
Context:
Explanation: 12:30 - 13:30 is in the system. I am not able to add a meeting with time slot from 13:30 to 14:30.
have to change to (13:31 - 14:30) for it to work.