Page MenuHomePhabricator

Enable recording of user Input for “Something else” incident category
Closed, DuplicatePublic

Description

Background

In the current version of the Incident Reporting System (IRS), when a user selects the “Something else” incident category, they are presented with a text area where they can describe their issue. However, this input is not currently recorded or stored.

To gather meaningful data on issues that do not fit into predefined categories, the system must record the user’s entry in this text field. This will help identify recurring themes, refine existing categories, and inform future improvements to the tool.

User stories

  • As a user who selects “Something else”, I want to be able to describe my issue in a text box, so that I can explain my situation even if it doesn’t fit existing categories.

Requirements

  • When the user selects “Something else”, display an editable text area
  • Record and store the user’s text input along with the selected category (Something else).
  • Limit input to a reasonable maximum length (no of characters TBD) to prevent abuse or data storage issues.

Designs

Acceptance criteria

  • TBD

Event Timeline

I'm dropping this back into needs refinement as I couldn't find the instrumentation spec for it, if one exists. @Madalina I've chatted with @phuedx from Data Platform Engineering about the best next steps/best practices for gathering this data and we concluded that one of the following two would be ideal:

  • Can we drop our character limit? It's set to 1000 right now but if we can live with 320, then we can use the default action schema. Next steps would be to deprecate our custom event schema, update the ingest code to pipe to the default schema. This would reduce the number of things we and Data Platform Engineering have to maintain.
  • Move forward with instrumenting what we're already collecting but not recording. Next steps would be to update our custom schema to take a custom field and adjust the ingest code to pipe it.

Additionally, I'd like to note that the survey response is not part of the v2 instrumentation spec being written.

-Next steps would be to deprecate our custom event schema, update the ingest code to pipe to the default schema.

FYI T408178: Decommission the Wikistories instruments is an example of such a deprecation. I can provide more examples and/or detail as necessary but the short of it is that there's a small change to remove the stream and then some tidy up work to be done by Data Platform Engineering.