Closed abroddrick closed 5 months ago
This is Ticket part 2 for Federal Agency changes
This ticket was carried over to sprint 44 in the "In review" status.
FYI we had approval on Friday from Zander for this ticket, but we decided not to merge due to the gulp issue (see Slack discussion here -- we are waiting for 2075 (the fix for the gulp issue) to be merged, and then we will merge this ticket as well.
(We also found a possible duplicate Federal Agency and are confirming if that should be removed + renamed as well)
Issue description
We created a Federal agency table that removed duplicate and incorrect values (ticket #1928). However, that ticket just created the table and filled it with the correct values, and it will be connected with the federal agency drop down in ticket #1793. However, some requests and domain information objects may be using the old agency names or invalid values that we do not to keep around. We should migrate any request or domain information to use the appropriate new federal agency name. This ticket can be done at the same time as 1793, but it's advised they be separated branches/PRs for ease of reviewing.
Acceptance criteria
Additional context
Note: the field that should be updated is the updated_federal_agency field and it should contain the foreign key to Federal Agency table
for unit testing, don't worry about testing every case, only test a couple of the cases
PR which added Federal Agency table
Items that need deprecating: Note "State, Local, and Tribal Government" should change to Non-Federal Agency. (it was removed entirely as an invalid option)
See below for the remaining (keep is what you should change any "remove" values to):
Links to other issues
relates to #1928 (ticket to add federal agency table- closed) relates to #1793 (ticket to connect federal agency table to the drop list- next ticket)