-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assign Bed throws error "Cannot create conflicting entry" even though no bed was allocated previously #6748
Comments
I want to work on this issue. Please assign it to me. |
@rithviknishad |
The bed eafefo was created on "2022-07-15T12:44:16.229074+05:30". Can the problem be related to the creation date of that bed? |
How would the creation date of that bed be a problem? It could be a problem with that specific bed, but what exactly is the problem? If it's vacant, then it should be assignable with current time right? |
Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity. |
@rithviknishad I am not able to recreate the issue, I can assign that exact bed |
@Pranshu1902 |
yeah, I guess that is intentional to block switching withing the same minute |
Describe the bug
Assign Bed throws an error "Cannot create conflicting entry" even though no bed was allocated previously
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If the bed is already occupied, the option for selecting such beds should be disabled by either showing "Occupied" badge or the bed should be hidden.
Otherwise, if there are no conflicting entries, it should allow to assign the bed.
Screenshots
The text was updated successfully, but these errors were encountered: