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 worked on initial reporting in #501 but some issues around deleted queues weren't able to be resolved. The current change exports all user queues whether or not they're deleted.
One idea was to include the deleted date on the csv report. This could probably be done by a change in the View SQL if joining against the officehours_api_queue. We left it out because we didn't have time to test this. This could also possibly be added in the code.
The other idea was for the UI to include a flag to filter deleted or active. This was originally added in the UI in #506 and removed in f660994.
I wasn't sure how to do this, however it seems like the SafeDelete package makes it easy so this should be possible to add in a future release.
# To retrieve all records including deleted ones
all_records = MyModel.all_objects.all()
# To retrieve only deleted records
deleted_records = MyModel.deleted_objects.all()
# To retrieve only non-deleted (active) records
active_records = MyModel.objects.all()
The text was updated successfully, but these errors were encountered:
We worked on initial reporting in #501 but some issues around deleted queues weren't able to be resolved. The current change exports all user queues whether or not they're deleted.
One idea was to include the deleted date on the csv report. This could probably be done by a change in the View SQL if joining against the
officehours_api_queue
. We left it out because we didn't have time to test this. This could also possibly be added in the code.The other idea was for the UI to include a flag to filter deleted or active. This was originally added in the UI in #506 and removed in f660994.
I wasn't sure how to do this, however it seems like the SafeDelete package makes it easy so this should be possible to add in a future release.
The text was updated successfully, but these errors were encountered: