Description
Describe the Bug
Scenario 1: Revert Application d2 to draft, cannot release decision because the 'Linked Request' field has no results
Scenario 2: Save draft decision with a Linked Request, but it disappears when you open the draft again
Expected Behaviour
The linked reconsideration or modification request should be present in the 'Linked Request' field when Review Outcome on the request is 'Proceed to Reconsider' or 'Proceed to Modify'
Actual Behaviour
Once the user either reverts the d2 to a draft or saves a draft then re-opens, the 'Linked Request' field is empty even though the Review Outcome on the request is 'Proceed to Reconsider' or 'Proceed to Modify'
** Steps To Reproduce**
Scenario 1 Steps to reproduce the behaviour:
- Revert a Application d2 to draft
- See the 'Linked Request' field has No Results
- Go to the Post-Decision tab, verify the request's Review Outcome field is 'Proceed to ...'
- User cannot re-release decision with empty 'Linked Request' field
** Steps To Reproduce**
Scenario 2 Steps to reproduce the behaviour:
- Create Application d2
- Create Application Reconsideration or Modification with Review Outcome that is 'Proceed to ...'
- Go back to d2, select the Reconsideration or Modification in the 'Linked Request' field
- Save the draft decision, then go back and edit decision
- Reconsideration or Modification request in the Linked Request field has disappeared and the field is empty, cannot be populated
- Decision draft will also not accept any further changes, "Failed to update decision" error toast
ONLY IMPACTING APPLICATIONS