feat: add timing metadata for case contacts #5919
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elasticspoon
force-pushed
the
feat/add-case_contact-metadata
branch
from
0d0ceb5
to
04bd7c6
Compare
elasticspoon
requested review from
compwron,
FireLemons and
littleforest
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have been attempting to improve the Case Contact flow but we don't have good data to tell if the changes we make are improvements or not. Ex: #5867 changed the form to use a dropdown but a user had complaints that it slowed her down because she had to select every contact type one at a time.
This PR adds a
jsonbfield to the case contact model that will hold metadata about the model. At the moment I want to just store what time the contact got changed to each status. The goal will be to use that data to track whether the changes we make are actually causing volunteers to spend less time at each case contact state.I am doing this as a
jsonbfield because I am not sure on the data I want to store now and in the future. I would also like this data to potentially be accessible via database query.