Write Task Available Actions Tech Spec

[lomky]

Description

We have found a multitude of issues and heartache around the Task model functions available_actions_unwrapper, actions_available?, and actions_allowable?.

• The names of the functions are unintuitive
• The usage of the functions is inconsistent and buggy in the code
• Programmers have a hard time generally know what the functions do and when to call them
• Different tasks implement the functions to different purposes.

This tech spec exists to create a small-scale remodel focused on bringing all the existing actions into alignment. Questions to be answered:

• Are all the functions necessary?
• When should each of the necessary functions be called?
• Are there more intuitive names for these functions?
• What does the breakout of the work look like?
• How do the existing tickets this is blocking fit in?

This tech spec does not exist to revamp the entire architecture of how we handle task actions. There is an potential tech spec for that larger effort already. This ticket's scope is much smaller, focused on figuring out how to make the existing code architecture consistent, comprehensible, and well-engineered.

[ajspotts]

What is this graph?

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

Standard 3 for Tech Spec.

[araposo-tistatech]

@lomky I see this one is in the Define pipeline, is there something specific here Product will need to have addressed with Stakeholders?

[lomky]

@araposo-tistatech I don't believe so! This should be shovel-ready