Task List, Filters, and Views

LadVen OS - the operating system for business helps a manager keep department work under control through the tasks section, and helps an employee quickly understand what to do today, which deadlines are at risk, and where new changes have appeared. On one screen, you can find the tasks you need, filter them by conditions, choose a convenient view, save repeatable slices, prepare an export, and change several tasks at once.

The main idea is simple:

• the list answers the question "what is in the work";
• filters clarify which tasks should be visible;
• views show tasks from different angles: table, Kanban, personal board, schedule;
• bulk actions help quickly restore order when the same decision applies to several tasks.

The tasks section should not be just a large registry. In LadVen OS, it works as a control panel for operational work: the manager sees risks, the employee sees a personal queue, and the business owner understands where the process needs attention.

What questions the tasks section answers

For a manager, the tasks section helps:

• see overdue work across the department;
• understand who is overloaded and who has free capacity;
• find tasks without an assignee;
• check priority and client tasks;
• prepare a slice for a planning meeting, report, or client meeting;
• quickly reassign tasks if plans have changed.

For an employee, the tasks section helps:

• assemble a personal work list for the day or week;
• check tasks where they are the assignee, co-executor, or observer;
• see new comments and changes;
• arrange tasks by deadlines and priorities;
• return to a task with active time tracking;
• avoid losing tasks without a deadline, estimate, or clarification.

Working slices for management

To make the tasks section useful every day, create several stable slices. They should answer repeatable management questions, not simply save a random set of filters.

Slice	Who uses it	What question it answers
My active tasks for today	employee	what needs to be done next
Unread with my participation	employee and manager	where new questions or decisions have appeared
Overdue by department	manager	which tasks already require intervention
Without assignee	manager	where work cannot move because there is no owner
In acceptance	creator or manager	which results need to be checked
High-priority client tasks	manager and process owner	which client commitments must not be lost
Tasks without deadline	manager	what has fallen out of planning
Weekly plan by people	manager	who is overloaded and who has capacity

Do not try to replace live management work with these slices. A slice shows where to look. The decision is still made after opening the task card and checking the context.

Task views

A view defines how to look at the found tasks. The same set of tasks can be opened as a list, Kanban board, or schedule. The choice depends on the question that needs to be answered.

List

The list is suitable for precise control: it is convenient for comparing tasks by fields, sorting, configuring columns, selecting several tasks, and preparing an export.

Use the list when you need to:

• find a task by number, title, client, or project;
• check deadlines, statuses, priorities, and assignees;
• prepare a working list for the team;
• assemble a reporting slice;
• change the same field for several tasks at once.

For daily work, keep only the needed columns in the list: title, assignee, status, deadline, priority, and nearest plan. For a report, you can add project, creator, planned and spent time, creation date, and update date.

Kanban

Kanban shows tasks by status. It is useful when it is important to understand the movement of work: what has not started, what is in progress, what is waiting for review, and what is already closed.

Kanban helps:

• see which status has accumulated the most tasks;
• quickly discuss the work flow at a team meeting;
• open a task card and clarify context;
• notice tasks that have not moved for a long time.

For precise column setup, exporting a table report, and bulk changes, the list is more convenient.

For a manager, Kanban is useful as a movement map, not as the place for the final decision. If many tasks accumulate in the "In review" column, the problem may not be with performers but with overloaded acceptance. If tasks stay at the beginning of the flow for too long, the task statement may be incomplete or there may be no clear assignee. If many tasks return backward, review readiness criteria, files, and comments.

Read Kanban from left to right as a flow of commitments, not as a set of separate cards:

• on the left, you see what has not yet been accepted into work or has no clear next step;
• in the middle, you see the real execution load;
• closer to acceptance, you see where the result is prepared but not yet confirmed by the requester or manager;
• on the right, you see completed work that can be used in a report or client reconciliation.

A bottleneck is the column where tasks accumulate faster than they move forward. For a manager, the reason matters as much as the count. If many tasks are in progress, check performer load and deadlines. If many tasks are in acceptance, check who must accept the result and whether cards contain enough readiness criteria, files, and comments. If many tasks return to rework, the issue may be in the task statement, result standard, or acceptance process, not in one specific task.

Review acceptance buildup separately. Do not move such tasks to completed in bulk only because they stand in one column. First open several cards from that column and separate them into groups:

• the result is ready and checked - close the task or record acceptance;
• the result exists, but a file, comment, or checklist part is missing - return it to rework with a concrete note;
• the result is no longer needed in the previous form - close it with an explanation or create a related task for the new result;
• acceptance is delayed by the manager or requester - assign a review time and do not leave the task without a decision.

For a business owner, this column shows not "how many tasks are almost ready", but how many results have not yet become accepted commitments. If acceptance regularly becomes the bottleneck, adjust the review rule: who accepts, by what deadline, by which criteria, and what counts as a sufficient result.

Use Kanban at a planning meeting like this:

1. Open a slice by department, project, or client direction.
2. See which statuses have accumulated tasks.
3. Compare the buildup with upcoming deadlines and people's load.
4. Open several tasks from the problem column and check the reasons.
5. Record decisions in task cards: comment, deadline, assignee, related task.
6. After the meeting, check that the status reflects the real state of work.

Do not move tasks between statuses just to make the board look clean. The status must show the working truth: the task is new, in progress, under review, returned, closed, or stopped for a clear reason.

Personal Kanban

Personal Kanban helps an employee arrange their tasks by work stages, and helps a manager see how the person organizes their personal queue. It does not replace task status, but it helps plan execution.

Use personal Kanban when you need to:

• assemble a personal plan for the day or week;
• separate tasks "in progress" from tasks "waiting for clarification";
• prepare for a one-on-one meeting;
• understand which tasks can be moved to another work stage.

If a task has several participants, the main assignee remains the owner of the result. Co-executors and observers help with context, but they should not blur control.

Weekly schedule

The weekly schedule shows tasks by day. It helps assess how deadlines are distributed over time and notice overload in advance.

The flow helps read the schedule as an early management tool: where deadlines cluster, who is overloaded, and what can be moved before work becomes overdue.

In the weekly schedule, check:

• tasks for the current week;
• overdue tasks that need to be returned to the plan;
• days with a high concentration of deadlines;
• tasks without an assignee;
• tasks without time or preliminary estimate;
• tasks that need to be moved before work starts.

This view is convenient for weekly planning and daily syncs. If you need to edit many fields or prepare a report, return to the list.

People schedule

The people schedule shows work relative to performers. This is the main tool for assessing department workload and preparing redistribution.

Use it when you need to:

• understand who is overloaded in the next few days;
• see tasks without an assignee;
• compare the plan between employees;
• prepare arguments for reassignment;
• check whether urgent tasks are concentrated on one person.

The people schedule answers the question "who does the work and when". If you need to understand which client tasks need attention, it is better to use a client filter and grouping by projects or clients.

For a manager, the schedule is most useful as an early intervention tool. If one employee has urgent tasks gathered on one day and there is free capacity nearby, do not wait for actual overdue work: open the card, check the context, reassign part of the work, or change the deadline together with the result owner.

Do not use the schedule only as a nice calendar. It must answer management questions: whether there are enough people for the promised volume, whether tasks without an assignee are stuck, and whether too much urgent work has appeared for one performer.

Search

Search is needed to quickly narrow the list by text: number, title, description fragment, client, or project.

Working order:

1. Enter a short query.
2. Wait for the result to update.
3. If there are too many tasks, add a filter by status, assignee, project, client, or deadline.
4. If there are no tasks, check active filters, saved slice, and selected view.

Search does not replace filters. Search answers the question "where does this text appear", while filters answer "which tasks match the conditions".

Quick filters

Quick filters cover the most frequent work questions. They help you get to the needed slice without complex setup.

Filter	When to use
Active	For the current queue without closed tasks.
Mine	To see tasks where you participate in the work.
With my participation	When you need to find tasks where you are not necessarily the assignee, but participate in discussion or execution.
Assigned	To focus on tasks with performers.
By department	For controlling tasks of a team or subdivision.
Unread	To process new comments and changes.
Overdue	For urgent deadline control.
Without assignee	To find tasks that cannot move normally without a result owner.
Priority	For tasks that need to be processed before the usual flow.
For the week	For planning the next few days and preparing a sync.
Require preliminary estimate	For tasks where the work volume must be agreed first.
All	For the full list, taking the other selected conditions into account.

Useful combinations:

• "Overdue + department" shows what the team must urgently process.
• "Client + active + high priority" helps highlight client tasks that need attention now.
• "Without assignee + project" shows where work is stuck because there is no owner.

Advanced filters

Advanced filters are needed when quick conditions are not enough. They let you specify status, priority, assignee, creator, project, client, deadline, creation date, or update date more precisely.

Use advanced filters for slices such as:

• active client tasks without an assignee;
• overdue high-priority tasks;
• tasks created or updated during the selected period;
• tasks by a specific creator in the selected project;
• tasks without a deadline that need to be included in planning.

A complex filter should be explainable. Before saving, ask yourself: "What work question does this set of conditions answer?" If the answer cannot be formulated, the filter will be difficult to maintain and explain to colleagues.

Saved slices

A saved slice remembers a repeatable set of conditions: search, filters, view, grouping, sorting, and visible columns. It is worth creating one if you regularly return to the same work question.

Saved slices fit scenarios such as:

• "My active tasks for the week";
• "Overdue by department";
• "Client tasks without assignee";
• "Tasks for review";
• "Project report";
• "Unread with my participation".

How to create a useful slice:

1. Configure search, filters, grouping, sorting, and view.
2. Check that the result answers a repeatable question.
3. Save the slice.
4. Give it a clear name without internal abbreviations.
5. Before deleting it, make sure the slice is not needed for regular control or reporting.

It is convenient for a manager to keep separate slices for department control, overdue work, client tasks, and reports. Employees benefit from slices for personal work, unread tasks, and weekly planning.

For shared management slices, establish clear rules:

• name the slice by the question it answers: "Department overdue", "In acceptance", "Without assignee";
• do not create several almost identical slices for one team;
• assign a slice owner if it is used at a planning meeting or in a report;
• when the process changes, update the existing slice instead of multiplying a new version without reason;
• an employee's personal slices should not replace shared department slices.

If the team argues about "which list is correct", it is a sign that slices have not been agreed. In LadVen OS, it is better to have fewer stable slices that everyone understands the same way than dozens of personal filters with different rules.

Active timers

Active timers show tasks where time tracking is currently running. They help you quickly return to work and notice a timer that was accidentally left on.

Use active timers when you need to:

• continue a task where work is already being tracked;
• check whether time tracking was started by mistake;
• see tasks where actual labor costs are already growing;
• prepare plan and actuals by tasks before a report.

If a timer is running on the wrong task, first open the task and check the context, then correct time tracking.

Quick task creation

Quick creation helps create a new task from the work context without extra navigation. This is convenient when, while reviewing a list, it becomes clear that an additional task, assignment, or template-based task is needed.

Before creating, check which slice you are working in. If the list is opened by client, project, or department, the new task may require checking links, participants, and deadlines.

Use a template when the task repeats a stable process: approval, check, document preparation, client launch, regular report. Do not use a template only for speed if its checklist, participants, or deadlines do not fit the current situation.

Groupings

Grouping changes the structure of the found tasks, but does not replace a filter. A filter selects tasks, while grouping arranges them into meaningful blocks.

Available groupings:

• no grouping;
• by clients;
• by projects.

Grouping by clients helps process the client flow, prepare a report by customer, and see tasks without client context.

Grouping by projects is useful for project control: which tasks belong to each project, where there is overdue work, and which projects need attention.

If a group is no longer needed in daily work, it can be hidden or collapsed so it does not interfere with viewing important tasks.

How to read grouping:

Grouping	What it shows	What risk to look for
No grouping	The general task queue by selected filters	Overdue work, no assignee, tasks without deadline
By clients	Load and commitments by clients	Client tasks without owner, overdue promises, tasks without CRM context
By projects	State of project flows	Projects with accumulated review, tasks without deadline, or uneven load

If a task falls into the "without client" or "without project" group, this is not always an error. But for client commitments and project work, a missing link interferes with reporting and future search. Open the task and check whether the context should be filled in.

Columns

Columns define which data is visible in the list. They should be chosen for the task: daily work needs a short set, while a report needs a fuller one.

Main columns:

• number;
• title;
• priority;
• assignee;
• nearest plan;
• creator;
• project;
• status;
• deadline;
• planned time;
• spent time;
• creation date;
• update date.

For daily work, keep only the fields by which you make decisions. If there are too many columns, the list becomes a heavy report rather than a working tool. It is better to create two saved slices: one for daily control and another for export or analysis.

Recommended column sets:

Scenario	Columns
Employee personal work	Title, status, deadline, priority, nearest plan
Department control	Title, assignee, status, deadline, priority, update date
Client control	Title, client, project, assignee, status, deadline, priority
Plan/actual and workload	Title, assignee, deadline, planned time, spent time, status
Report or export	Number, title, status, deadline, assignee, creator, project, client, planned time, spent time, creation and update dates

If a user manually enables the same columns every time, save the slice. This way the team will look at the same set of data instead of arguing why the list looks different for different people.

Sorting

Sorting helps you quickly find what matters inside the already filtered tasks.

Common options:

• by deadline - to see the nearest and overdue tasks;
• by update date - to find recently changed tasks;
• by priority - to raise critical tasks;
• by assignee - to check distribution;
• by status - to assess execution flow;
• by project or client - if the list is being prepared for a report.

Do not rely only on sorting if you need to exclude unnecessary tasks. First set a filter, then sort the result.

Export

Export is needed to transfer tasks outside LadVen OS, prepare a report, or reconcile data. You can export all found tasks or only the visible part of the list.

Before export, check:

• the correct saved slice or set of filters is selected;
• search has not left an accidental restriction;
• grouping matches the report;
• visible columns reflect the needed fields;
• sorting helps read the export;
• closed or unnecessary tasks did not get into the list.

If a field is critical for the report, check the export immediately after it is generated. During export, wait for the operation to finish before starting a new export.

Data refresh

Refresh is needed when new task data may have appeared: comments, status change, deadline change, new assignee, file upload, or timer start.

Refresh the list:

• after long work on an open screen;
• before a reporting meeting;
• after a bulk change;
• if a colleague said they changed a task;
• before exporting a critical list.

If data changed after refresh, rely on the fresh result.

Actions on one task

Quick actions for a specific task are available in the list row or mobile card. They are convenient when the decision depends on the content of one task: open it, check context, go to a related object, change status, or perform an available action.

If you need to change many tasks in the same way, use bulk actions. If each task requires a separate decision, process them one by one.

Bulk actions

Bulk actions are needed for uniform changes to several tasks. They save time when the decision has already been made and is the same for all selected tasks.

A bulk action is safe when the list is first narrowed to tasks with the same meaning and the result is checked after the change.

With them, you can:

• select individual tasks;
• select all visible tasks;
• change assignee;
• change status;
• change priority;
• change project;
• change client;
• change deadline.

Use bulk actions only where tasks have the same work meaning. If the context differs, first narrow the list with filters or process tasks one by one.

Examples of safe use:

• assign one assignee to tasks without an owner within one project;
• move the deadline for a group of tasks with an agreed new plan;
• change priority for tasks that a manager has marked as urgent;
• close identical tasks after checking the result.

After a bulk change, check the result. Some tasks may not change because of permissions, task state, or required conditions. Such tasks need to be opened separately and the cause reviewed.

On a mobile screen, first make sure you can see the selected tasks and understand which action you are applying. Do not start a bulk change if the selection is unclear.

Partial result of a bulk action

A partial result means the system changed not all selected tasks. This is a normal protective situation: tasks may have different permissions, statuses, required conditions, or guard checks.

How to act:

1. Do not repeat the bulk action on the whole set immediately.
2. See which tasks changed and which remained unchanged.
3. Open the unapplied tasks and check the reason: permissions, status, required field, guard check, change conflict.
4. Fix the reason only where it is truly needed.
5. Repeat the action for the remaining tasks as a separate smaller set or process them manually.

Example: a manager selected ten tasks without an assignee and assigned an owner. Seven tasks changed, three did not: one was already closed, one is in a project without change permission, and one triggered a guard check. The correct decision is to review those three tasks separately, not repeat the assignment for all ten.

For a manager, a partial result is not only an error list. It shows where the same management decision stopped being the same for every task:

• if rights block the action, check who owns the process or project;
• if status blocks the action, check whether the task really belongs in the selected slice;
• if a guard check blocks the action, open the card and complete the missing condition;
• if another participant changed the task, compare the current state before retrying.

After review, split the remainder into smaller groups. One group can receive the same bulk action again; another group may need a comment, a separate owner decision, or no change at all.

For more about such situations, see Errors, limits, and unavailable actions.

Empty, loading, and error states

The tasks section should help users understand why tasks are not displayed and what to do next.

Loading

During loading, do not conclude that there are no tasks. Wait for the update to finish or check the state indicator.

Empty list

An empty list can mean different situations:

• there really are no tasks;
• the selected filters found no results;
• the search query is too narrow;
• a saved slice hides the needed tasks;
• a group is collapsed or hidden;
• the wrong view is selected.

Correct diagnosis:

1. Reset search.
2. Check quick filters.
3. Check advanced conditions.
4. Open the full list if you need the entire task set.
5. Check grouping and the selected view.
6. Refresh data.

Error

A list error means data could not be loaded or refreshed. An action error means a specific operation was not applied.

What to do:

• retry refresh;
• check whether access permissions have changed;
• narrow the filter if the request is too broad;
• after a bulk action error, open several tasks and check their actual state;
• before repeating export, make sure the previous export finished or clearly failed.

If the error is related to access, the user may see the list without some data or may be unable to open a specific task.

Daily work

For daily work, it is useful to keep several simple slices instead of one complex filter for all cases.

Recommended morning order:

1. Open the "My active" or "With my participation" slice.
2. Check unread tasks.
3. Look at overdue tasks.
4. Switch to the week to see upcoming deadlines.
5. Check tasks with preliminary estimate.
6. Open Kanban or schedule if you need to assess the work flow.
7. Refresh data before making decisions.

For a team manager:

• use the department filter;
• check tasks without an assignee;
• review overdue and priority tasks separately;
• use the people schedule to assess workload;
• save separate slices for control and reporting;
• apply bulk actions only after checking context.

For a performer:

• start with the personal work list;
• keep columns to a minimum;
• sort by deadline;
• use the weekly schedule for planning;
• check unread tasks before starting work;
• record tasks without deadline or clarification so they do not fall out of the plan.

Regular manager control

For a manager, it is important not just to open the task list, but to go through it in the same order. Then control becomes predictable and does not turn into manual status collection.

Recommended weekly review order:

1. Open a slice by department or direction.
2. Check overdue tasks and delay reasons.
3. Find tasks without an assignee, deadline, or clear next step.
4. Open tasks in acceptance and decide: close, return for revision, or clarify criteria.
5. Look at the people schedule and assess overload.
6. Check client and priority tasks separately.
7. Record changes in task cards, not in personal chats.
8. Save or update the slice if the regular question has changed.

During such a review, do not change tasks in bulk only because they appeared in one list. First make sure they have the same context and the same management decision.

For a business owner, not all operational details are useful. Several signals matter:

• how many tasks are overdue in key directions;
• whether there are tasks without an assignee;
• which client commitments are at risk;
• where work has accumulated in acceptance;
• which processes regularly require manual intervention;
• which tasks repeat and should become a template or automation.

If the same slice shows the same problem every week, it is a reason to change the process, not just review the list again.

Preparing a report

A reporting list must be reproducible: another user should understand which conditions were applied and why the export looks exactly this way.

Preparation order:

1. Define the report question: client, project, department, performer, deadline, status, or overdue work.
2. Configure filters for this question.
3. Choose grouping: by client, by project, or without grouping.
4. Enable reporting columns: number, title, status, deadline, assignee, creator, project, planned and spent time, creation and update dates.
5. Sort the list so it is easy to read.
6. Save the slice if the report is needed regularly.
7. Refresh data.
8. Export all found tasks or the visible part of the list.
9. Check the export: task set, columns, sorting, and absence of an accidental search query.

Do not use bulk actions while preparing a report if the goal is only to view data. Bulk actions change tasks, not report structure.

Quick scenarios

Find overdue team tasks

1. Open the task list.
2. Enable the "Overdue" filter.
3. Add a department filter.
4. Sort by deadline.
5. Check assignees in the column or open the people schedule.

Prepare a client report

1. Select the client.
2. Keep active tasks or the needed statuses.
3. Group by projects if the client has several directions.
4. Enable status, deadline, assignee, planned time, and spent time columns.
5. Refresh data.
6. Export the found tasks.

Process tasks without an owner

1. Enable the "Without assignee" filter.
2. Add project, client, or department if the list is too broad.
3. Open tasks where context is needed.
4. Assign an assignee in bulk only for tasks with the same result owner.

Check a performer's week

1. Open the weekly schedule or people schedule.
2. Select the needed assignee or department.
3. Check deadline concentration by day.
4. Find overdue and priority tasks.
5. Move or reassign tasks only after checking context.

Prepare for a department planning meeting

1. Open the saved department slice.
2. Check overdue and priority tasks.
3. Look at tasks without an assignee.
4. Open the people schedule and assess workload.
5. Record tasks that need to be reassigned, moved, or discussed separately.

Process the personal queue

1. Open the personal slice.
2. Sort tasks by deadline.
3. Check unread changes.
4. Move tasks without a deadline into the weekly plan.
5. Set aside tasks that are waiting for clarification, and leave only a clear queue in work.

Common mistakes

Working from the full list. The full list quickly turns into noise. Daily work needs slices for a specific question.

Saving overly complex filters. If a slice cannot be explained in one sentence, colleagues will not understand why exactly these tasks are in it.

Treating overdue work as the only risk signal. A task without an assignee, deadline, next step, or acceptance also needs attention.

Changing tasks in bulk without checking context. The same status in a list does not mean the same management situation.

Making a report from a random screen state. Before export, check search, filters, grouping, sorting, and columns.

Using Kanban as a replacement for the task card. Kanban shows movement, but decisions, files, comments, and acceptance remain in the card.

Not refreshing data before a meeting. An old list creates a false picture of workload and deadlines.

Good practices

• Keep separate slices for personal work, department, overdue work, acceptance, and client tasks.
• Start review with risks: overdue work, no assignee, no deadline, unread changes.
• Open the task card before an important decision.
• Use the people schedule to redistribute workload, not to look for someone to blame.
• Before a bulk change, narrow the list with filters to tasks with the same meaning.
• For a report, save a reproducible slice so it can be repeated later.
• If a slice regularly shows the same problem, turn it into a template, regulation, or automation.

What screenshots are needed for documentation

A full task list guide needs screenshots not only of the general list, but also of working management states.

Screenshot	Why it is needed
General list with quick filters	show the starting screen and the basic way to narrow tasks
Advanced filters	explain exact task search conditions
Saved slices	show regular working sets for a manager and employee
Kanban by statuses	show the task execution flow
Weekly schedule	show deadline planning by day
People schedule	show team workload control
Bulk actions	show safe changing of several tasks
Export	show preparation of a reporting list
Empty list after filter	show diagnosis of filters and search

These screenshots should gradually be captured for all LadVen OS languages. The Russian set remains the structural reference, but the public version for each language should show the localized interface.