-
Notifications
You must be signed in to change notification settings - Fork 8
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
Provide an overview of the notificatie responses per abonnement #180
Labels
Comments
alextreme
added
enhancement
New feature or request
good first issue
Good for newcomers
triage
labels
Aug 20, 2024
Estimate: 1 day, also it would be useful to see the URL of the abonnement in the listview filter instead of the UUID |
danielmursa-dev
added a commit
that referenced
this issue
Dec 24, 2024
danielmursa-dev
added a commit
that referenced
this issue
Dec 24, 2024
danielmursa-dev
added a commit
that referenced
this issue
Dec 24, 2024
danielmursa-dev
added a commit
that referenced
this issue
Dec 24, 2024
danielmursa-dev
added a commit
that referenced
this issue
Jan 2, 2025
danielmursa-dev
added a commit
that referenced
this issue
Jan 2, 2025
github-project-automation
bot
moved this from Implemented
to Done
in Data en API fundament
Jan 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Debugging issues for DH, I often miss having an overview of the notification responses for a specific subscription/abonnement.
The easiest way to get this currently is by trying to delete an abonnement, which first gives you a list of the notification responses sent for the abonnement / the deeplinks to the notification responses. But this approach isn't for the faint of heart :)
Adding /admin/datamodel/notificatieresponse/ to the main menu, showing the datetime of the notification in the listview and using raw_id_fields in the detail view should make investigating the notification responses a lot more workable. Currently the detailview times out with DH.
The text was updated successfully, but these errors were encountered: