View Reminder History and Acknowledgement Status per Assignment
For accountability and audit purposes — especially relevant for Bufdir reporting and for organizations like Blindeforbundet with formal assignment tracking requirements — coordinators must be able to view a timeline of all reminder events on an assignment. The timeline should show automated reminders, manual reminders, delivery status (sent/delivered/failed), peer mentor acknowledgement (opened notification), and any subsequent contact events. This history must be stored persistently and not deleted when the assignment is closed.
User Story
Acceptance Criteria
- Given a coordinator opens an assignment detail, when they scroll to the history section, then all reminder events appear in chronological order with timestamps, type (auto/manual), and delivery status
- Given a push notification was opened by the peer mentor, when the coordinator views the history, then the acknowledgement is shown with a timestamp indicating when the peer mentor opened the notification
- Given a reminder delivery failed (e.g., FCM token expired), when the coordinator views the history, then the failed delivery is shown with a failure indicator and the fallback action taken
- Given an assignment is completed or closed, when a coordinator views it later, then the reminder history is still fully accessible and not purged
- Given the assignment history is accessed, when it loads, then the data renders within 2 seconds even for assignments with 20+ reminder events
Business Value
Creates an auditable paper trail for compliance with organizational policies and Bufdir documentation requirements. Protects coordinators from disputes about whether follow-up was attempted. For Blindeforbundet's formalized assignment model with delivery and read receipts, this history is a core functional requirement, not a nice-to-have.