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
When attorneys are ready to check a case out to their judge, they need to add decisions (issue + disposition) for each request issue.
AC
Attorneys:
When the attorney clicks "Decision ready for review", they navigate to the new Add decisions screen (and not the Select dispositions screen that exists for legacy appeals)
Judges:
This is replicated for judges. When the judge clicks "Ready for dispatch", they navigate to this page. However, let's title it Review decisions instead of Add decisions like we do for legacy.
Both:
Populate all request issues on the Add decisions screen per mocks
A button exists beneath each request issue, per mocks.
When there isn't a note captured by Intake, hide the "Notes" field.
Mocks
The text was updated successfully, but these errors were encountered:
Connects: #7966, Resolves: #7965, Resolves: #7957, Resolves: #7958
### Description
This change actually makes the add/edit decision issue modal functional. It saves results to the redux store and sends them to the server on completing the flow. It also updates the remand reason select screen to work with these new decision issues.
It also displays decision issues on the case details and disposition selection screen.
### Testing Plan
1. Don't break existing functionality
Part of Editing AMA issues
When attorneys are ready to check a case out to their judge, they need to add decisions (issue + disposition) for each request issue.
AC
Attorneys:
Add decisions
screen (and not theSelect dispositions
screen that exists for legacy appeals)Judges:
Review decisions
instead ofAdd decisions
like we do for legacy.Both:
Mocks
The text was updated successfully, but these errors were encountered: