Existing Tasks Functionality overview.

[gshif]

• [x] Go over the existing tasks documentation to get yourself familiar with the tasks functionality: http://docs.internal/specifications/requirements/
• [x] Get together with the existing tasks team : Lyon and Emrys and discuss requirements of the existing functionality of the tasks service/component.
• [x] Get together with PM (Russ?) and get the requirements.
• [x] Get familiar with current test coverage for both OSS/IDPE.

The end result of this exercise should be a document describing the requirements of tasks

[gshif]

• Have an initial doc describing current coverage.

[kevinhogan111]

2) POST /tasks create a task  (covered) 
3) GET /tasks/{taskID} retrieve a task  (covered) 
4) PATCH /tasks/{taskID} update a task (covered) 
5) DELETE /tasks/{taskID} (covered) 
6) GET/tasks /{taskID} /runs Retrieve list of run records for a task (covered, Used by UI) 
7) POST/tasks /{taskID} /runs manually start a run of the task now overriding the current schedule.  (Not covered, used by UI)
8) GET/tasks /{taskID} /logs Retrieve all logs for a task (not covered, used by UI) 
9) GET/tasks /{taskID} /runs /{runID} /logs Retrieve all logs for a run (not covered, used by UI)
10) GET/tasks /{taskID} /labels list all labels for a task (not covered) 
11) POST/tasks /{taskID} /label add a label to a task. (Not covered) 
12) DELETE/tasks /{taskID} /labels /{labelID} delete a label from a task (not covered) 
13) GET /tasks /{taskID} /members List all task members (not covered) 
14) POST/tasks /{taskID} /members Add task member (not covered) 
15) DELETE /tasks /{taskID} /members /{userID} removes a member from an task (not covered) 
16) GET/tasks /{taskID} /owners List all task owners (not covered) 
17) POST /tasks /{taskID} /owners Add task owner (not covered)  
18) DELETE /tasks /{taskID} /owners /{userID} removes an owner from an task (not covered) 
19) GET task by orgID (not covered, used by UI) ```

[gshif]

@kevinhogan111, I would argue that create tasks, for example, is not fully covered (just to have in mind when you'll be testing APIs)