Allow individual queue folks to place tasks on hold

[lpciferri]

The Translation organization just got their first AMA appeal translation task assigned to them! However, the only actions they have available to them are Re-assign to person, Assign to team, or Mark task complete. We need to add the Place on hold option

Acceptance Criteria

• Translation team individuals (and other repeatable queue individuals, like hearing branch individuals) can place tasks assigned to them on hold
• Team admins can place tasks assigned to them or to their organizations on hold
• For cases that have been placed on hold, users have all actions they had available to them when the case was in their assigned tab (in the assigned status), plus:
  • End hold - this (1) completes the hold task and (2) changes the task's status to "assigned" so the task appears in the user's assigned tab (instead of on hold tab)

Screenshot from demo

[lowellrex]

Let's try to use the TimeableTask model here to accomplish this if we can.

[lowellrex]

MEDIUM.

[amprokop]

The organization view doesn't have an "on hold" tab for tasks, so @lowellrex and I think we might need to not allow tasks assigned to organizations to be put on hold.

[lpciferri]

here's the ticket to add on hold tab to team queue - #9341

is this something that you could take on as well?

[lpciferri]

@lowellrex - i'm unassigning @amprokop from this task. let's connect today or tomorrow about how we might finish this ticket this or next sprint!

[lowellrex]

Rough rollout plan:

• Create new TimedHoldTask (Create TimedHoldTask #10499)
• Add endpoint for creating timed holds (Add endpoint for creating timed holds #10570)
• Make sure GenericTasks respond properly to having a child TimedHoldTask (End holds set with timed hold tasks #10687)
  • "Days on hold" appears correctly
  • Actions display correctly (all of the same actions as before + "Cancel timed hold")
  • Updating the parent task cancels the TimedHoldTask (are there any scenarios where this is not true?)
• Add "Place task on hold" option to tasks that don't already have that option (Enable all tasks to be placed on timed hold #10728)
  • Create modal similar to the existing on hold page for ColocatedTasks
  • Continue using existing system for ColocatedTasks
• Move creation of new timed holds for ColocatedTasks to TimedHoldTasks (Replace old style holds with TimedHoldTask #10861)
  • Do not allow ColocatedTasks to have their holds ended until all holds put on the old way have expired (or been migrated to the new way)
• Remove code that assumes old-style holds. Ticketed as Remove old-style hold code and db column #10896.
• Remove the vestigial on_hold_duration column from the tasks table. Ticketed as Remove old-style hold code and db column #10896.
  • Wait until all old-style holds have expired before doing this so we don't have to migrate any holds from the old-style to the new style. Queries that demonstrate when we are okay to drop the old style columns (https://caseflow-looker.va.gov/sql/g6f2tszfv3g2hn and https://caseflow-looker.va.gov/sql/ty7pnnrfzccftk).
  • Save data from any columns we will delete to a file or database table so we retain the option to recover that information.
• Run the timed hold expiration job more frequently (hourly instead of daily). Ticketed here.

Tech spec for TimedHoldTask creation API design (#10512)

[lowellrex]

MEDIUM amount of work remains.