-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update existing data requests #2503
Update existing data requests #2503
Conversation
I havent added in the below areas as they dont exist in the live data SECURITY_DATA_REQUEST_TYPES = %w[g2_security g3_security].freeze |
request.update!(data_request_area_id: data_request_area.id) | ||
|
||
# TEMP LOGGING INFO | ||
Rails.logger.debug "Updated DataRequest ##{request.id} - #{request.request_type}, with data_request_area_id: #{data_request_area.id} (area_type: #{data_request_area_type}, contact_id: #{data_request_area.contact_id}, data_request_area.user_id: #{data_request_area.user_id}, data_request_area.case_id: #{data_request_area.case_id}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left in for local testing purposes, will remove when ready
The script used to generate data requests for local testing purposes. This has to be used as creating a DataRequest normally through the service, no longer gives a value to
|
…858-update-existing-data-requests
…ministryofjustice/correspondence_tool_staff into cdpt-1858-update-existing-data-requests
# Get the data_request_area_type for this request | ||
data_request_area_type = data_request_area_type_for(request.request_type) | ||
|
||
Rails.logger.debug "Finding DataRequestArea with user_id: #{request.user_id}, case_id: #{request.case_id}, contact_id: #{request.contact_id.presence}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left in for local testing purposes, will remove when ready
db/data_migrations/20241024131255_migrate_data_request_areas.rb
Outdated
Show resolved
Hide resolved
db/data_migrations/20241024131255_migrate_data_request_areas.rb
Outdated
Show resolved
Hide resolved
db/data_migrations/20241024131255_migrate_data_request_areas.rb
Outdated
Show resolved
Hide resolved
…858-update-existing-data-requests
…858-update-existing-data-requests
…858-update-existing-data-requests
…858-update-existing-data-requests
…858-update-existing-data-requests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you remove the debug logging then this should be ready to merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
1d04c1e
into
cdpt-1850-commissioning-and-chase-redesign
Description
All existing data requests need to be associated to their relevant data request area
Self-review checklist
CT-7654 ...
Screenshots
Related JIRA tickets
https://dsdmoj.atlassian.net/jira/software/c/projects/CDPT/boards/1152?selectedIssue=CDPT-1858
Deployment
Manual testing instructions