> MUST: The web interface must provide an overview of the various workflows (recently completed, recently failed, in-process, waiting-decision) with easy navigation, sorting and filtering The goal here is to provide the security / release team with an overview of their packages that need review or attention. This almost certainly needs some more requirements investigation via #394. This feature should also cater to the needs of other teams with non-interactive workflows like the wanna-build team. They should be able to see all their "BuildAndUpload" workflows, analyze the recently failed ones and possibly retry the failed work requests, etc (see #379 for a related ticked dropped from M3). Things to consider: - should the workflow list (or workflow view) offer an easy way to open `/work-request/` with a filter so that it lists only work requests that are inside a given workflow ? we already support a "status" filter there, we likely need more (at least `workflow_parent`, but maybe also by `task_name`, etc.) - the entry point is likely some list of "WorkflowTemplate" because a given team will want to monitor all the workflows created out of a set of specific workflow templates. - the list of workflows and work-requests should probably become workspace specific --- Included tasks: - [x] rework the web UI to be workspace centered (#557) - [x] rework the WAIT task creation to document the "needs_input" workflow_data key - Don't forget to update documentation - [x] add supplementary filters to `/<scope>/<workspace>/work-request/` - [x] create the new view/template for `/<scope>/<workspace>/workflow/` (depends on #618 for the correct list) - [x] Save WorkflowTemplate.name in the created WorkRequest (#618) (needed for the list of workflows) Please refer to https://freexian-team.pages.debian.net/debusine/reference/devel-blueprints/monitor-workflows.html for details.