In app feedback

[manio143]

Getting feedback is important to improve the service. Some issues will be caught during testing and development, but some (such as inconvenience) are more likely to be reported by users themselves.

Why not link users to a Google doc (forms)? We already have user email and they agree to the Privacy Policy when registering for the ref hub, I don't see a good reason to store that info elsewhere.

Feedback data

• user id or NULL (allow anonymous feedback)
• Feedback text
• Timestamp
• Page user was on
• Admin notified flag
• Feedback addresses/ignored flag

User UX

An icon next to the user menu in the top navigation panel, which when clicked presents a dialog: "Provide feedback:" title, text area, anonymous checkbox (toggled off by default), submit button, cancel button.

Clicking cancel or outside the dialog should close it, preserving the state until page refresh, to prevent loosing data when accidentally closing.

Clicking submit will, disable the text area and submit button, trigger a background API request, upon completion showing a banner above the buttons, indicating success or error (for error case include session id and email for manual contact).

Admin notification

A job would aggregate all feedbacks not acted upon (marked addressed or ignored) and not previously sent over, older than 3-5 days (to be determined), and compose an email to all admins with UserFeedbackAdmin role. Then mark those sent items by setting Admin notified flag to true.

Admin UX

A new tab in the admin portal would be present for those with the UserFeedbackAdmin role and IQA Admin role.

Non anonymous feedback would be decorated with user details to allow contacting them if clarity of feedback is necessary. A way to mark feedback as addressed or ignored should be present.

Retention

Feedback should be retained for up to 180 days, with a daily cleanup job removing ols entries. Unaddressed feedback should be sent again to admins every 30 days.

[manio143]

An MVP would be simpler:
submitting the feedback should schedule a background job that sends email to the tech alias including user id, user email, user name, diagnostic id, page it happened on and the message.