Allow tasks to block dispatch

[hschallhorn]

Connects #14055 and #14661

Following discussions on various implementations on blocking dispatch tasks, echo engineers have chosen a solution which we feel will cover the desired blocking scenarios and be the least likely to cause disruption to other areas of the codebase.

The solution revolves around determining the status of a blocking task's appeal prior to its creation, which in return will determine whether the task is created on the BvaDispatchTask or the RootTask.

BvaDispatchTask

• If there is an open BvaDispatchTask assigned to a user, the blocking task should be created as a child to this task. In this instance, the dispatch task shall be placed on hold which prevents the user from completing it and places it into the users on hold tab.

RootTask

• If the appeal does not have an open BvaDispatchTask, the blocking task should be created directly on the RootTask.

Other necessary steps

• Additionally, in the locations (here and here) where we are creating BvaDispatchTask, we need to do a check for the existence of any of the blocking tasks and prevent the creation of the dispatch task if they do exist (e.g. tasks.open.blocks_dispatch.any?).

• Finally, when the blocking task has been completed we need to proceed with the creation of the BvaDispatchTask. If the logic for not creating a dispatch task is captured in create_from_root_task then we do not need to check for open blocking tasks anywhere else.

[araposo-tistatech]

Replaced by #14661

[hschallhorn]

#14661 is just the tech spec. This ticket exists to implement solutions that fall out of the tech spec

[yoomlam]

what is this chart?

1 | 
2 | 
3 | |||||
5 | |||||||
8 | 

Multiple PRs probably

AC

• Certain tasks will have the ability to block dispatch (updating actual tasks to use this logic will come later - don't update tasks to cause blocking)
• These task should be created under RootTask or BvaDispatchTask
• BvaDispatch tasks are not created when tasks that block dispatch are still open
• BvaDispatchTask is created when all tasks that block dispatch are closed

Why 3?

• Testing!!

Why 5?

• Convoluted logic around determining the parent for a mail task
• several moving parts

[lomky]

Placing back into Team queue - work is engineered & reveiwed, but awaiting gov partner feedback & implementation of the case of post-decision appeals handling. Slack thread

[araposo-tistatech]

@lomky Per the Board:

"None of the tasks below should block a motion to vacate and they can move simultaneously:

CongressionalInterestMailTask
FoiaRequestMailTask
PrivacyActRequestMailTask
PrivacyComplaintMailTask
FoiaColocatedTask
FoiaTask
PrivacyActTask"

[yoomlam]

Additional AC:

• Notify Reporting Team of changes to the 'cases-ready-for-distribution' logic via a new ticket in the dsva-vacols repo

The Reporting Team (TIB) has a report showing cases that are ready for distribution, which uses the blocking-task logic discussed in Case Distribution Blocking Tasks #75. If we change this logic, we need to notify the Reporting Team so they can update their queries. Slack convo