Portfolio user can view and update suborganization for their portfolio. Suborganization is a required field for the Portfolio.
Acceptance criteria
[ ] Under Domain Management for a domain in a portfolio, the suborganization side nav link is clickable and takes you to the suborganization page
[ ] the suborganization page matches this figma be sure to scroll to the right to see the full flow.
[ ] Portfolio user can update and save suborganization for this domain (this saves to domain information)
[ ] provide save successfully message to user
[ ] sub orgs shown in the drop down are only ones that are linked to the current portfolio.
[ ] Portfolio user can not leave suborganization field blank
[ ] Portfolio user can search the suborganization from drop-down
[ ] provide reset the search- if the person clicks the x on the search then the x returns the box to the initial input value.
[ ] The suborganization edit button on the overview page should take a user to the suborg page.
Additional context
When we make portfolios for orgs, we will need to ensure that this field is never empty, this implementation assumes we did that correctly. However, I suggest adding a log if for some reason this field is empty when the user goes to the given page.
Issue description
Portfolio user can view and update suborganization for their portfolio. Suborganization is a required field for the Portfolio.
Acceptance criteria
Additional context
When we make portfolios for orgs, we will need to ensure that this field is never empty, this implementation assumes we did that correctly. However, I suggest adding a log if for some reason this field is empty when the user goes to the given page.
Links to other issues
blocked by #2365 blocked by #2354