Do not update AOD motions if they do not apply to the appeal #14087
Labels
Feature: case-details
Priority: High
Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work.
Product: caseflow-queue
Source: BVA Reported
Stakeholder: BVA
Functionality associated with the Board of Veterans' Appeals workflows/feature requests
Team: Echo 🐬
Type: Bug
Milestone
This is a quick patch before getting to #14085.
Description
When we check the AOD status of an appeal, we check their age
caseflow/app/models/person.rb
Lines 12 to 14 in 43562ed
caseflow/app/models/advance_on_docket_motion.rb
Lines 19 to 25 in 43562ed
Currently, when an AOD team member attempts to mark a case as AOD, it completes successfully, but the current case is not shown as AOD. This is because we update the existing AOD motion
caseflow/app/models/advance_on_docket_motion.rb
Line 28 in 43562ed
Instead, we should only update AOD motions that were created after the appeal was received.
Also, as age related aod motions should apply at the claimant level and be granted for all subsequent appeals, do not update any age related aod motions.
Acceptance Criteria
create_or_update_by_appeal
should only update aod motions that would apply to the current appealcreate_or_update_by_appeal
should not update reason for age related aod motionsThe text was updated successfully, but these errors were encountered: