Page MenuHomePhabricator

Implement database storage for incident report submissions
Open, Stalled, Needs TriagePublic

Description

We will want to record submissions from the Incident-Reporting-System in a database table for a few reasons:

  • Prevent duplicate submissions
  • Ensure we have our own copy in case of Zendesk failure
  • For the future: provide the possibility for tracking the resolution of an incident report, for the reporter as well as for users who are able to view the report
  • For the future: be able to use report submission metadata in other tooling

The table should be private (not exposed in replicas) and contain provisions for regular purging after X days (to be discussed with L3SC).

Columns would include:

  • Unique ID (some kind of UUID so people can't work out how many submissions have been sent)
  • Free text comment from the report
  • User ID of the reporter
  • User ID of who is being reported
  • Relevant revision ID
  • Which options were selected in the form from emergency/non-emergency flow

Event Timeline

kostajh renamed this task from Record submissions in database table to Implement database storage for incident report submissions.Sep 7 2023, 10:38 AM
kostajh updated the task description. (Show Details)
kostajh updated the task description. (Show Details)

This is not for the MVP. @Madalina do we have another task tree / milestone where we can place this task?

kostajh changed the task status from Open to Stalled.Mon, Dec 9, 8:31 PM

I think the next step here is documenting why we want to do this, thinking through retention policies, clarifying what we want to store, and then filing an L3SC task. We should probably file a task to track the design/product specification/L3SC approval, and then this task can just be about the engineering implementation. I'm marking this task as Stalled, for now.

  NODES
Note 1
Project 4
USERS 1