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
We recently added pagination to the schedules endpoint and the client side filtering on status no longer works accordingly.
We should change it so that the backend endpoint takes a parameter to filter out schedules based on whether the schedules are used in escalation chains or not (All, Used in Escalations or Not Used) - the same we're doing it now except it's on client side.
Involves backend for adding the endpoint change and frontend for passing the parameter.
The text was updated successfully, but these errors were encountered:
We recently added pagination to the schedules endpoint and the client side filtering on status no longer works accordingly.
We should change it so that the backend endpoint takes a parameter to filter out schedules based on whether the schedules are used in escalation chains or not (All, Used in Escalations or Not Used) - the same we're doing it now except it's on client side.
Involves backend for adding the endpoint change and frontend for passing the parameter.
The text was updated successfully, but these errors were encountered: