build about:support models

RESOLVED FIXED

Status

Input Graveyard
Backend
P1
normal
RESOLVED FIXED
3 years ago
11 months ago

People

(Reporter: willkg, Assigned: willkg)

Tracking

Details

(Whiteboard: u=dev c=feedback p=1 s=input.2014q4)

In order to capture about:support data, we need a new table to put it in.

This bug covers:

1. figure out requirements for storage
2. create the Django model for about:support data
3. write any useful tests
4. add code to our data deletion cron job
5. update relevant documentation

Comment 1

3 years ago
@willkg please provide more details about this bug. I would like to work on this. I think if I get to know exactly what to do then I can fix this.

Explain more what this bug is all about. What is about:support data? I didn't get that.
Flags: needinfo?(willkg)
This bug isn't fleshed out because I don't know what the requirements are, yet. Thus it's not ready to be worked on, yet.
Clearing the needsinfo on this one.
Flags: needinfo?(willkg)
Grabbing this to work on now.

I need to figure out what's available in the API and then talk to the UA folks to see what they want to capture.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Talked to the UA folks. They said it's ok to stick it in a text field as a JSON object blob. So... I'm going to do that. Plus we'll just stick it all in (aka defer what we're putting in the blob until we implement the form changes).

We don't need additional tests, yet, so I'm skipping that.

Added it to the purge_data script.

In a PR: https://github.com/mozilla/fjord/pull/406
Whiteboard: u=dev c=feedback p= s=input.2014q4 → u=dev c=feedback p=1 s=input.2014q4
Blocks: 1104935
Landed in https://github.com/mozilla/fjord/commit/f984935f5ecff70a15d886d08fd7deee44e94146

I'll wait to deploy it since it doesn't do anything unless the form changes are there, too.
Pushed to prod just now.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.