Task Documentation Coverage

This map keeps task documentation aligned with everything the UI supports, not only the basic creation flow. For each window, track the user scenario, the good practice, and the screenshot that proves the flow.

Coverage Rule

Every task block needs:

• a scenario article or article section;
• visible fields, actions, and states;
• practices: when to use it, how to avoid noise, how to check the result;
• localized screenshots under static/img/<locale>/...;
• an entry in screenshot-manifest.json.

Windows and Blocks

Window or route	Cover	Practices	Screenshots
/tasks	task list, search, filters, presets, grouping, refresh, export, bulk actions	keep the work list useful without losing urgent tasks	planned
/tasks?create=1	creation: title, description, assignee, deadline, participants, project, client, documents, files, checklist	define a result, choose one owner, attach useful files, split work into steps	planned
/tasks?taskId=<id>	task drawer: details, status, participants, files, checklist, comments, context history	keep work decisions inside the task instead of private messages	planned
/tasks?taskId=<id>&mode=edit	editing fields, participants, deadline, files, checklist	when to edit a task and when to create a related task	planned
/tasks/:taskId	standalone task page	when to open and share a task link without losing context	planned
task checklist	items, order, nesting, groups, completion	build a checklist as a process, not a long description	planned
task files	attachments, useful materials, versions, private data, documents and links	what counts as a useful attachment	planned
participants	creator, assignee, co-assignees, observers	assign roles without blurring responsibility	planned
comments	questions, decisions, files, mentions	keep decisions in task context	planned
statuses and closing	result check, completion, return for revision	close only after checking the result	planned
task views	list, kanban, personal kanban, schedule	choose the right view for personal, team, and deadline control	planned
relations	project, client, CRM, documents, related and child tasks	connect work so context can be found from the task	planned
templates	repeatable tasks and starter field sets	use a template instead of manual copying	planned
automation	task rules and automation history	automate repeatable actions without hidden side effects	planned
time and timers	time tracking, timer, time entries	separate planned work from actual time spent	planned

First Screenshot Set

Required first screenshot ids:

• tasks.create-task.light-desktop;
• tasks.create-task.files-light-desktop;
• tasks.create-task.checklist-light-desktop;
• tasks.view.comments-light-desktop;
• tasks.view.checklist-light-desktop;
• tasks.list.filters-light-desktop;
• tasks.kanban.light-desktop;
• tasks.schedule.light-desktop.

Definition of Done

A task article is ready when it covers every visible block of the window, explains the workflow and not only the buttons, includes a result check, links related actions, avoids private data, has screenshots or planned manifest status, and is translated into every portal language.