Caseflow: Determine what to do with children of cancelled tasks assigned to inactive users

[hschallhorn]

Spun out of #12483.

Some slack chatter.

In some scenarios, when we "reassign" tasks of an inactive user, some tasks are merely cancelled to be reassigned manually by a judge, team admin, quality reviewer, bva dispatch team member, etc. On occasion these tasks will have children that become orphaned due to their parent being cancelled. In some scenarios, these children can be moved to their new parent. In other scenarios, these downstream children should be cancelled.

This ticket exists to determine which path to take in which situation.

AC

• [x] Plan to handle children of cancelled tasks is created
• [ ] Properly handling these children is specced out with another ticket(s) to do the work

[lomky]

Throwing a 2 at this after scoping it to planning out the work needed.

[araposo-tistatech]

@hschallhorn,

Can you confirm the below are the only parent/child task associations we will run into in this case?

“PARENT TASK”, “CHILD TASK”
[[“JudgeAssignTask”, “AttorneyTask”],
[“JudgeDispatchReturnTask”, “AttorneyDispatchReturnTask”],
[“BvaDispatchTask”, “JudgeDispatchReturnTask”],
[“QualityReviewTask”, “JudgeQualityReviewTask”],
[“JudgeDecisionReviewTask”, “AttorneyTask”],
[“JudgeDecisionReviewTask”, “AttorneyRewriteTask”],
[“JudgeQualityReviewTask”, “AttorneyQualityReviewTask”]]

[hschallhorn]

Here are the scenarios and the number of times the scenario occurs (investigation)
A judge leaves the board and the following tasks are cancelled, leaving orphaned child tasks

• [ ] JudgeAssignTasks with child ColocatedTasks (257)
• [ ] JudgeQualityReviewTasks with child ColocatedTasks (22)
• [ ] JudgeDispatchReturnTasks with child ColocatedTasks (5)
• [ ] JudgeQualityReviewTasks with child AttorneyQualityReviewTasks (86)
• [ ] JudgeDispatchReturnTasks with child AttorneyDispatchReturnTasks (21)

An attorney leaves the board and the following tasks are cancelled, leaving orphaned child tasks

• [ ] AttorneyTasks with child ColocatedTasks (2152)
• [ ] AttorneyRewriteTasks with child ColocatedTasks (127)
• [ ] AttorneyQualityReviewTasks with child ColocatedTasks (18)
• [ ] AttorneyDispatchReturnTasks with child ColocatedTasks (5)

A QualityReview team member leaves the board and the following tasks are cancelled, leaving orphaned child tasks

• [ ] QualityReviewTasks with child JudgeQualityReviewTasks (151)

A judge leaves the board and the following tasks are cancelled, leaving orphaned child tasks

• [ ] ChangeHearingDispositionTasks with child TranscriptionTasks (1)
• [ ] ChangeHearingDispositionTasks with child EvidenceSubmissionWindowTasks (1)

A LitigationSupport team member leaves the board and the following tasks are cancelled, leaving orphaned child tasks

• [ ] VacateMotionMailTasks with child PulacCerulloTask task (1)

[hschallhorn]

Suggestions

1. Move the orphaned child tasks to the parent task
   
   
   
   • [ ] JudgeQualityReviewTasks child ColocatedTasks move to parent QualityReviewTask
   
   
   • [ ] JudgeDispatchReturnTasks with child ColocatedTasks move to parent DispatchTask
   
   
   • [ ] AttorneyTasks with child ColocatedTasks move to new JudgeAssignTask
   
   
   • [ ] AttorneyRewriteTasks with child ColocatedTasks move to parent JudgeDecisionReviewTask
   
   
   • [ ] AttorneyQualityReviewTasks with child ColocatedTasks move to parent JudgeQualityReviewTask
   
   
   • [ ] AttorneyDispatchReturnTasks with child ColocatedTasks move to parent JudgeDispatchReturnTask
   
   
   • [ ] ChangeHearingDispositionTasks with child TranscriptionTasks move to parent HearinqTask
   
   
   • [ ] ChangeHearingDispositionTasks with child EvidenceSubmissionWindowTasks move to parent HearinqTask
   
   
   • [ ] VacateMotionMailTasks with child PulacCerulloTask task move to parent VacateMotionMailTask
   
   

1. Cancel these tasks as new QR or dispatch tasks will be created for the judge or quality review team member

   • [ ] JudgeQualityReviewTasks with child AttorneyQualityReviewTasks
   • [ ] JudgeDispatchReturnTasks with child AttorneyDispatchReturnTasks
   • [ ] QualityReviewTasks with child JudgeQualityReviewTasks

2. Still pondering this one as the case moves back to the distribution pool. We don't want to move the admin action to the distribution tasks as that will block it from being distributed to a new judge

   • [ ] JudgeAssignTasks with child ColocatedTasks (257)

[araposo-tistatech]

@hschallhorn can you explain what you mean by the first option "Move the orphaned child tasks to the parent task"? My moving it to the parent task do you mean moving it to the user that has that parent task?

[hschallhorn]

Here is an example!

Currently: Say an attorney leaves the board and there is a AttorneyDispatchReturnTask assigned to them that will now be cancelled and it has a downstream OtherColocatedTask (admin action). This would make the parent JudgeDispatchReturnTask "assigned" and able to be assigned to a different attorney, but leaves an open OtherColocatedTask. This could leave us with a colocated task that never gets completed before the appeal is dispatched.

Proposed: "Move the orphaned child tasks to the parent task" means we will make that JudgeDispatchReturnTask the parent of the previously orphaned OtherColocatedTask tasks. VLJ support an continue working this OtherColocatedTask and the judge can assign the a AttorneyDispatchReturnTask to a new attorney once the admin action is completed.

Task trees

BEFORE REASSIGN

Appeal 17635 (direct_review)                    STATUS    ASGN_TO
└── RootTask                                    on_hold   Bva
    └── BvaDispatchTask                         on_hold   BvaDispatch
        └── BvaDispatchTask                     on_hold   VACOWILLIW
            └── JudgeDispatchReturnTask         on_hold   VACOCARACA
                └── AttorneyDispatchReturnTask  on_hold   VACOPARKT
                    └── OtherColocatedTask      on_hold   Colocated
                        └── OtherColocatedTask  assigned  VACOAUSTIT1

AFTER CANCELLING (CURRENT)

Appeal 17635 (direct_review)                    STATUS    ASGN_TO
└── RootTask                                    on_hold   Bva
    └── BvaDispatchTask                         on_hold   BvaDispatch
        └── BvaDispatchTask                     on_hold   VACOWILLIW
            └── JudgeDispatchReturnTask         assigned  VACOCARACA
                └── AttorneyDispatchReturnTask  cancelled VACOPARKT
                    └── OtherColocatedTask      on_hold   Colocated     <- Orphaned 
                        └── OtherColocatedTask  assigned  VACOAUSTIT1   <- tasks

AFTER CANCELLING (PROPOSED)

Appeal 17635 (direct_review)                    STATUS    ASGN_TO
└── RootTask                                    on_hold   Bva
    └── BvaDispatchTask                         on_hold   BvaDispatch
        └── BvaDispatchTask                     on_hold   VACOWILLIW
            └── JudgeDispatchReturnTask         on_hold   VACOCARACA
                ├── AttorneyDispatchReturnTask  cancelled VACOPARKT
                └── OtherColocatedTask          on_hold   Colocated
                    └── OtherColocatedTask      assigned  VACOAUSTIT1

[araposo-tistatech]

@hschallhorn regrets, realized I did not add the Boards thoughts to this ticket. They agree with the first two suggestions and would like for the colocated tasks to remain active even if the cases is assigned back to distribution.

[araposo-tistatech]

@hschallhorn please let me know if further definition is needed here.

[hschallhorn]

would like for the colocated tasks to remain active even if the cases is assigned back to distribution

The open question is where these should move to. If they remain where they are, the case could be dispatched without the work being completed. If the move to under the distribution task, they will block distribution.

[araposo-tistatech]

Sent email to the Board inquire where the colocated tasks should move to.

[araposo-tistatech]

What is the concern of having the colocated tasks block distribution? The Board feels this might be the better option since the attorney and/or VLJ would not be able to work the case until those are completed anyway, but they will confirm this with the DVCs.

[hschallhorn]

That is true! If that's what the board would like moving forward, that works for me! Happy to finally have a resolution for this

[hschallhorn]

Resolution:

1. Move the orphaned child tasks to the parent task
   
   
   
   • [ ] JudgeQualityReviewTasks child ColocatedTasks move to parent QualityReviewTask
   
   
   • [ ] JudgeDispatchReturnTasks with child ColocatedTasks move to parent DispatchTask
   
   
   • [ ] AttorneyTasks with child ColocatedTasks move to new JudgeAssignTask
   
   
   • [ ] AttorneyRewriteTasks with child ColocatedTasks move to parent JudgeDecisionReviewTask
   
   
   • [ ] AttorneyQualityReviewTasks with child ColocatedTasks move to parent JudgeQualityReviewTask
   
   
   • [ ] AttorneyDispatchReturnTasks with child ColocatedTasks move to parent JudgeDispatchReturnTask
   
   
   • [ ] ChangeHearingDispositionTasks with child TranscriptionTasks move to parent HearinqTask
   
   
   • [ ] ChangeHearingDispositionTasks with child EvidenceSubmissionWindowTasks move to parent HearinqTask
   
   
   • [ ] VacateMotionMailTasks with child PulacCerulloTask task move to parent VacateMotionMailTask
   
   

1. Cancel these tasks as new QR or dispatch tasks will be created for the judge or quality review team member

   • [ ] JudgeQualityReviewTasks with child AttorneyQualityReviewTasks
   • [ ] JudgeDispatchReturnTasks with child AttorneyDispatchReturnTasks
   • [ ] QualityReviewTasks with child JudgeQualityReviewTasks

2. Move to block new distribution task

   • [ ] JudgeAssignTasks with child ColocatedTasks (257)