Work through clear states
Tasks use Pending, In progress, Blocked, and Completed states. Mobile presents horizontally snapping columns, while desktop retains the current list and board choices.
Coordinate shared work with status, priority, dates, assignees, labels, subtasks, effort, filters, and focused detail.
Ideas often disappear when responsibility, timing, and progress live somewhere else. Tasks adds an operational layer inside the community, with enough structure to coordinate programmes and projects without turning every member interaction into a project-management dashboard.
Tasks use Pending, In progress, Blocked, and Completed states. Mobile presents horizontally snapping columns, while desktop retains the current list and board choices.
Normal, High, Urgent, and Low priority combine with start and due dates, due-soon context, overdue status, and timeframe filters to make attention visible.
Assignee search presents selected members and query results without trapping the main page in a nested scroll area. Current roles determine who can create, assign, edit, and drag tasks.
Subtasks can carry their own title, description, completion state, and eligible assignee. Labels and effort remain available as compact supporting structure rather than overwhelming the primary task.
Task detail presents identity, state, description, completion and progress, followed by a quiet details area for secondary properties that have not already been shown.
Add the title and description, then set state, priority, timing, people, labels, effort, and subtasks.
Search or filter the board by status, timeframe, priority, and other current controls.
Managers use the supported drag interaction or edit controls to change state.
Update task and subtask progress while retaining the full detail and assignment context.
Role gates determine who can create, edit, assign, reorder, or change task state.
Tasks owns its mobile header and creation action so the generic community composer does not overlap the task workflow.
When Tasks is disabled, task routes show the current unavailable behavior and return the member to the community.
Tasks are free for every community. Creation, assignment, drag behavior, and editing follow the current member, manager, and creator permissions.
The information and actions remain aligned, but mobile is board-only with snapping status columns. Desktop retains list and board modes.
Yes. Current task forms and detail support multiple subtasks with their own completion and supporting information.
Those actions follow the current community and task role gates. The UI does not expose manager-only drag or edit behavior to every member.
The route uses the established feature-disabled response and returns the member to the community instead of rendering an empty task system.