Fix priority logic for appeals with aod motions for appeal attribute caching #15353
Labels
Feature: generic-queue
Priority: Medium
Blocking issue w/workaround, or "second in" priority for new work.
Product: caseflow-queue
Stakeholder: BVA
Functionality associated with the Board of Veterans' Appeals workflows/feature requests
Team: Echo 🐬
Type: Bug
Description
Now that AOD motions should be associated with an actual appeal (#14085), we need to adjust the logic for what we consider priority for cached appeal. This is still looking for motions associated with the claimant that were created after the appeal was established.
caseflow/app/jobs/update_cached_appeals_attributes_job.rb
Lines 238 to 247 in 00c4a75
Acceptance criteria
aod_based_on_age
is true on the appealNotes
The first 3 AC have a lot of overlap. What should we consider as our source of truth as I assume we don't want to check all 3?
Background/context/resources
Related: #15352
Technical notes
The text was updated successfully, but these errors were encountered: