-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tech Spec] Allow attorneys and judges to edit decision issues and set dispositions #7761
Comments
Yeah, there are some additional questions here. Like, can there be a decision with a benefit type different from the request? For HLRs and SCs the benefit type is specified up front. |
I would think a request issue would not have a decision issue until it's actually been decided, meaning there should not be a decision issue for all request issues |
I would prefer to add this when it becomes needed in the UI. I think this ticket should be about setting up required structure |
@shanear wrote:
is it fair to provision a decision issue to hold the disposition ahead of time though? I.e. it would be a placeholder for a decision that will happen eventually. The EDIT: I see that |
If this helps, I'm cool with this. I just don't think we should create the |
connects #7761 ### Description * Do not try and update DecisionIssues during RatingIssue sync. * Allow for null `rating_issue_reference_id` to support nonrating decisions
Currently, attorneys and judges can set dispositions on request issues but have no way of editing these issues. We need to introduce decision issues to allow for that.
Allowed Scenarios:
Assumptions:
Parameter example for scenario 1:
Parameter example for scenario 2:
Parameter example for scenario 3:
Parameter example for scenario 4:
Tech notes:
Add BE validation to validate request issue disposition based on the combination of dispositions for the decision_issuesAdditional Columns and migrations:
decision_issue
for eachrequest_issue
that is currently in production and that has a dispositionremand_reasons
table referencesrequest_issues
. If we start usingdecision_issues
, we need to migrateremand_reasons
to referencedecision_issues
instead.rating_issue_reference_id
indecisions
- doneThe text was updated successfully, but these errors were encountered: