Backfill data from fraud boolean columns to fraud timestamp columns#8237
Merged
Backfill data from fraud boolean columns to fraud timestamp columns#8237
Conversation
…th updated_at changelog: Internal, Data migration, backfill profile timestamps in fraud review or rejected
2 tasks
jmhooper
approved these changes
Apr 18, 2023
Contributor
jmhooper
left a comment
There was a problem hiding this comment.
Like we discussed, we may want to run the body of these as part of a roll-plan to get ahead of the release schedule.
6 tasks
This file contains hidden or 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
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.
🎫 Ticket
https://cm-jira.usa.gov/browse/LG-9399
🛠 Summary of changes
This PR creates a rake task to backfill fraud-related timestamps based on the corresponding fraud boolean fields.
Rollplan: run the following:
rake profiles:backfill_fraud_timestamps_from_booleans