You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The schedule exceptions functionality is missing the resource field, which is crucial for proper data handling. Additionally, the "Add Exception" button is not functioning as intended, preventing users from successfully adding exceptions. Furthermore, the "Delete" button in the schedule template is not working, making it impossible to remove existing templates.
To Reproduce
Steps to reproduce the behavior:
Go to 'schedules button on sidebar'
switch to Availability
toggle to exceptions and click add exception
Expected behavior
The resource field should be present and functional in the schedule exceptions feature to ensure proper data handling
The "Add Exception" button should work as intended, allowing users to successfully add new exceptions.
The "Delete" button in the schedule template should function correctly, enabling users to remove templates when needed.
Screenshots
problem 1
problem2
problem3
Desktop (please complete the following information):
OS: [windows]
Browser [chrome]
Version [131.0.6778.109]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
The schedule exceptions functionality is missing the resource field, which is crucial for proper data handling. Additionally, the "Add Exception" button is not functioning as intended, preventing users from successfully adding exceptions. Furthermore, the "Delete" button in the schedule template is not working, making it impossible to remove existing templates.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
problem 1
problem2
problem3
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: