You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fixtures_requests.py still hardcodes a string organization_name for our created Domain Requests. Now that organization name is tied to Portfolios, this leads to some some fixtures Domain Requests' organization names being incorrect.
Domain Requests created within a Portfolio still have the organization name as a hardcoded value from fixtures_requests.py (eg "Example - Withdrawn") instead of the actual portfolio's organization name. This generally gets corrected when assigning an organization name to a Domain Request on the UI, but in the edge case we assign a suborganization, instead of an organization, to a Domain Request the error persists.
Acceptance criteria
Update fixtures so that Domain Requests' organizations reflect the portfolio they are assigned to in fixtures.
Additional context
No response
Links to other issues
No response
The text was updated successfully, but these errors were encountered:
Issue description
fixtures_requests.py
still hardcodes a stringorganization_name
for our created Domain Requests. Now that organization name is tied to Portfolios, this leads to some some fixtures Domain Requests' organization names being incorrect.Domain Requests created within a Portfolio still have the organization name as a hardcoded value from
fixtures_requests.py
(eg "Example - Withdrawn") instead of the actual portfolio's organization name. This generally gets corrected when assigning an organization name to a Domain Request on the UI, but in the edge case we assign a suborganization, instead of an organization, to a Domain Request the error persists.Acceptance criteria
Additional context
No response
Links to other issues
No response
The text was updated successfully, but these errors were encountered: