97 average number of days db work only #16331
Merged
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.
Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.
Summary
Related issue(s)
Testing done
What areas of the site does it impact?
No other code was touched in this except the schema file to include the new table creation. This will be used for chatbot to display the average number of days to claim completion.
Acceptance criteria
Requested Feedback
We are going to be creating a github action to insert records into the new table. This will only run ONCE per week so we are looking at a very small footprint of data in the database. There is a desire to keep the historical records in the database however, there is no discussion of data retention at the moment as the current schedule would mean that we would expect to run for 20 years before we even had 1000 records. If we need an index on the
created_at
in order to speed up the DB request, we can make that change.