Skip to content

Tasks


title: "Tasks" description: "Create, assign, and manage tasks with rich fields, priorities, relations, and subtasks."

Section titled “title: "Tasks" description: "Create, assign, and manage tasks with rich fields, priorities, relations, and subtasks."”

A task represents a unit of work that can be assigned, progressed, and tracked. It supports rich fields, priority levels, relationships, and subtasks.

My Tasks is your personal task list across boards. By default it shows tasks assigned to you.

The list groups by due time: Overdue, Today, This week, Later, and No due date. Overdue stays at the top. Use Group to switch back to board groups. Saved My Tasks views remember the choice (HTPR-6455). Board split tabs still filter inside a time group.

Improvement The Scope button in My Tasks and the standard Scope command in Ctrl+K now open the same board picker list. The panel has been redesigned to match the board picker you use throughout the app, with search and standard keyboard navigation for quick filtering and selection. The previous, custom implementation has been replaced with the consistent board picker experience.

You can select multiple tasks in the My Tasks view using the keyboard shortcut G, followed by M, to enter multi-select mode. This mirrors the selection behavior from the Kanban board for a consistent workflow.

Once in multi-select mode:

  • Verify your selection: Each task you want to act on is checked. If viewing a filtered list, only tasks that are both checked and visible are included in the action.
  • Apply bulk actions: The following actions are available at the bottom of the list:
    • Archive
    • Assign
    • Label
    • Move to column
    • Delete
  • Unselect: Press G again or press U to exit multi-select mode.

Selected rows persist until you commit an action, so you can review the working set before bulk-actioning multiple tasks.

Tip: The selection model matches the way you select tasks in Kanban, so if you are comfortable bulk-archiving or moving tasks on a board, the pattern transfers directly to My Tasks.

To temporarily hide tasks from your My Tasks view, set a snooze. When you snooze until a date:

  • The task no longer appears in My Tasks until that date passes
  • The snooze date sets a calendar reminder so you can resurface the task later

A snooze is per task and independent of other views. Tasks remain otherwise accessible from boards, calendars, and saved views.

You can create and manage saved views on My Tasks to customize what you see. These views support:

  • Full filtering: Filter by title, assignee, priority, due date, labels, and more. Filter options match the Kanban board filter menu, so you can use familiar screen-level controls directly on My Tasks.
  • Sorting: Sort by any of the same fields, with priority as the primary sort key.
  • Board selection: Show tasks from one board or across multiple boards.
  • Done columns hidden by default: Done columns are hidden within each view to focus on active work.

Saved views persist at the account level and can be used as templates for board filter setups.

When you toggle a filter, sort order, or board, your selection is saved with the view. The next time you open that view, the settings are applied automatically. You can create multiple views for example, one for active prioritized tasks, one for a specific project, or any combination that matches your workflow.

To create a saved view, open My Tasks and use the view toolbar to pick filters and sorting options, then select Save view. The view appears in the saved views list alongside system views like Involvement and All tasks.

To hide distracting or temporary tasks:

  • Use View filters to show or hide assignments, priorities, or tags that don't match your current focus.
  • Create and pin a custom view with the exact criteria you want to see.
  • Review tasks by tag or priority and archive or move them away when no longer relevant.

Note: Saved views are scoped to the current team. Cross-board filters and sorting are supported, so you can see, for example, all high-priority inbox tasks across all boards in a single custom view.

The All Tasks view provides an at-a-glance overview of every active task across the board. It builds split views for each board section (To Do, In Progress, Done, etc.) from a single source of truth.

To access this view, navigate to the board and select All Tasks from the view toolbar.

All Tasks uses a single fetch pass that loads rows once and builds board splits from those rows. As a result:

  • Each board sees its own split of the task list.
  • Quiet boards do not lose splits in favor of busy boards.
  • The view is stable and deterministic across sessions.

Since All Tasks is board-wide, it aggregates tasks from all active columns and sections, making it useful for a quick health check or high-level tracking when you need to see everything that matters—not just what's pinned or currently in one section.

Note: Unlike My Tasks saved views, All Tasks does not automatically filter out onboarding, demo, template, and staging content, so those tasks may appear in the list. For visibility filtering, see Board & Subtask Visibility.

When searching within a board or in saved views, you can now narrow results using search operators on fields:

  • from: Restrict to tasks created by a specific user.
  • assignee: Restrict to tasks assigned to a specific person.
  • in: Restrict to tasks in a board, section, or column.
  • label: Restrict to tasks with a specific label.
  • is: Narrow by task type; for example, is:card to show only standard cards.
  • dates: Show tasks with dates matching a condition (by default, by due), or filter by due date ranges.
    • dates:2026-09-30 For tasks with that exact due date.
    • dates:<2026-09-30 For tasks due before.
    • dates:>2026-09-30 For tasks due after.
    • dates:in-range 2026-09-01..2026-09-30 For tasks due within the range.
    • dates:overdue For tasks marked overdue.
    • dates:today For tasks due today.
    • dates:this-week For tasks due within the current week.
    • dates:later For tasks due later than the current week.
    • dates:todays For tasks due on today and the day prior.
  • has: Show tasks that have a value in a field; for example, has:due-date for tasks that have a due date (including empty values) or has:assignee for tasks that have someone assigned.
  • Combining multiple operators is supported—for example, from:alice label:urgent dates:>2026-09-30 to find urgent tasks created by Alice after a certain date.

To apply search filters:

  1. Open Kanban or Table View.
  2. On the board header (or in the saved view toolbar), select Filter.
  3. Choose a field and an operator, then enter a value or pick from the options.
  4. Repeat for additional filters to narrow the list.

Search filters apply at the board level in Kanban and in saved views. The available operators depend on the board's configuration.

New The search bar includes:

Behavior change The My Tasks toolbar now uses icon-only controls with tooltips for Involvement, Columns, Scope, Filters, Sort, and Group. Active controls turn blue like Kanban, and Group shows its current choice (HTPR-6938). Overdue tooltips on red counts now appear over each overdue item. The toolbar also uses the same Save view and Reset controls as Kanban board views.

From the Ctrl+K command palette, you can still use Save view as to create a saved view, and Reset view to revert My Tasks to its default set of built-in filters. Keyboard shortcuts like Ctrl+S and Ctrl+R no longer open popovers on the board; they now open the Save view and Reset dialogs respectively.

This change makes view management across My Tasks and other board views more consistent, and ensures My Tasks mirrors the primary board interface.

From a board or inbox, click New task (or use the keyboard shortcut Ctrl+N / Cmd+N). This opens the task creator with the following top-level sections:

  • Title: The name or headline of the work.
  • Description: Optional text explaining what to do.
  • Assignees: One or more members to get notified and held accountable.
  • Sections & Columns: Drag the task to a section or use the section picker dropdown.
  • Due date: Pick a date or use predictive phrases like "tomorrow," "next week," or relative periods.
  • Priority: Choose Low, Medium, or High.
  • Estimated time: Optionally specify hours or a low-high range if needed.

Use Write with AI (Ctrl+K / Cmd+K, or the command palette) in the description area to turn a brief task idea into a fleshed-out task.

New The task creator window (formerly the "Compose" button) can be opened from any view with Ctrl+J / Cmd+J and is now live for everyone. The window behaves like a task creator with Search and New Task tabs, Ctrl+K and Ctrl+J tooltips, and Tab/Shift+Tab switching. It retains your old window size and grows as you type, and the New Task button is renamed to New Task (HTPR-6937).

Fix When the AI writer fails to generate a task, the Ctrl+J New Task box and the AI Task Writer now show the real failure reason instead of hiding it; your note is still saved as a task. If AI generation is not available, the text you entered appears without modification. This applies to task creation from boards, the inbox, and description editing in task details.

Some fields are type-checked before submission. For example, the ranking parameter must be a string; passing a number will fail with an error.

When Hypertask connects to a board from an external site or app, Hypertask now shows an approve screen first. The screen names the connector and the exact site that will receive access, letting you confirm before any access is granted.

This prevents a signed-in user from inadvertently granting external sites access to their entire board without prior approval.

Open a task to view and edit all its fields. Unsupported columns or fields may be hidden based on your team's board configuration.

Assign a clear priority (Low, Medium, or High) to reflect the task's importance and replacement cost. Higher priorities should be shown ahead of lower ones in lists, table view, and filters.

  • Added assignees trigger notifications to the task's assignees. If no assignee is specified, the task is unassigned.
  • Workers can have their own assignee field, tracked separately from human assignees. Workers appear in the Relationships section under the Workers relation type.

Click a date to pick another date or remove it. The date affects due date pickers and filter views. Predictive phrases like "tomorrow," "next week," and relative periods also persist.

Type hours or a low-high range for time-tracking integration.

Drag tasks between sections to change their column. This can trigger auto-assign rules if configured. In Table view, you can also drag any row onto another section's card; the row is the drag handle, the section card is the drop target, and the change surfaces immediately in both views (Column sort must be off for this to work; on /my-tasks, rows are grouped by time or board, so dragging doesn't target a section directly).

To edit the task description:

  • On desktop: Click or tap the description area, then edit.
  • Mobile: Double-tap the description to open the editor; a single tap remains in read mode.

If you are the Task Reporter (see below), you can edit the description directly. Only the Task Reporter can edit the description.

With the Task Reporter, anyone on the task can update the task description directly. The Task Reporter indicator visually appears alongside comment headers, making it clear who has opened the description for editing just like comments.

  • Task Reporter is available to any human assignee or worker on a task. The feature is not available for closed tasks.
  • When you open the description in edit mode, you become the Task Reporter for that task.
  • Only the Task Reporter can edit the description. This prevents concurrent edits and restores the semantic meaning of "owner of the description field".
  • If you close the description without saving any changes, the status clears and the next person to open it becomes the Task Reporter.

This model ensures a clear ownership of the description field, similar to comment ownership, which helps teams coordinate around tasks without stepping on each other's work.

Note: While you are the Task Reporter, you cannot switch to another task description edit until the current edit state closes, preserving a single active description edit at a time.

  • To remove an attachment, open the description in edit mode, click the attachment you want to remove, and save. Only the items you deselect will be removed; remaining attachments are preserved as one copy each.

Fix A previous bug caused the wrong attachment files to be saved when removing items from a description. When you had two or more description files attached, removing one would incorrectly save a duplicate of the other file. This is now fixed so that always only one copy of each remaining attachment is saved. (HTPR-6629).

Fix Deleting a task no longer creates an invalid undoable state. Undo is now always possible when restoring from deletion, ensuring tasks can be fully recovered and the undo system behaves consistently.

Fix Undo functionality has been consolidated under a single restoring rule. This ensures that restoring tasks after deletion behaves the same whether you use the Undo button or Ctrl+Z, with consistent behavior tracked through the board's undo history.

When you make manual changes to a task—"moving, assigning, unassigning, archiving, or deleting"—Hypertask cancels any active agent lease on that task and persists the change. Human modifications take priority over agent tasks, but agent-versus-agent collision protection remains in place. This ensures your task updates are never blocked by an agent while you're working.

Open a task to see:

  • Header with title, status section, assignees, workers, priority, and due date.
  • Description area with optional attachments.
  • Sections: Comments, Relations, Subtasks, Times, and Pages.
  • Task Reporter indicator marking who can edit the description.
  • Top bar with instant navigation and actions:
    • ← Back to task — Settings-style back button for navigation. On mobile, the back control matches the app's mobile back style with normal side spacing, making it easy to tap and fully visible up to 390px wide.
    • Save — Only right-aligned action remaining in the top bar; Delete is now moved to the Undo action in the Actions section.

Tasks can link to GitHub pull requests. The pull request section displays each linked PR with its status:

  • Open, Merged, Closed: Show the current status as reported by GitHub.
  • Last observed: The last-known status before the page loads.
  • Fetching...: Indicates a background refresh is in progress.

Improvement Tasks with linked PRs now show any saved PR status immediately—Open, Merged, or Closed—without waiting for GitHub to respond. Queries to GitHub run in parallel in the background and update the panel once the fetch completes, keeping the page fast and responsive. If you navigate away and come back, the PR panel refreshes again to stay current.

This change eliminates wait times for tasks with linked PRs and provides an instant-open experience even when GitHub fetches are slower than usual.

Security Hypertask now verifies that incoming PR updates come from known GitHub accounts before accepting them. By default, this restriction applies only to board 15. Except for board 15, an updated PR can link to any public repository, and the update is accepted as long as it originates from a trusted GitHub account. For board 15, only PR updates from three specified accounts are permitted: Valentin Yeo and two others configured by the board team. This prevents unauthorized actors from creating, moving, or commenting on tasks in board 15 via external PRs.

The comment thread shows all comments on the task. By default, when you open a task with comments, the newest comment remains expanded so you can see the latest conversation.

Link handling Plain web addresses in ticket descriptions and comments (http:// or https://) are automatically transformed into clickable links. Detects addresses based on recognized URL patterns, ensuring links in work notes and teammate discussions remain navigable on both desktop and mobile.

Performance improvement When you open a task, comments now load once instead of twice. The initial SSR data used as the starting point, with React Query configured to skip a second fetch if the data is fresh. This eliminates redundant data handling and speeds up task loads: repeat visits are now approximately 0.6 seconds faster. New and edited comments still appear automatically without a reload, and realtime invalidation, reconnect reconciliation, and window-focus refresh continue to work as expected.

Improvement Long task pages and comment threads now send their initial snapshot only once, reducing data copies and decoding passes. Repeat visit times drop from roughly 2.2 seconds to about 0.6 seconds. The change applies to tasks with many comments or long descriptions and focuses on the initial load speed, preserving all existing behavior for navigation, real-time updates, and comment handling.

Fix The comment box on ticket pages is now positioned immediately below the last comment instead of appearing in the middle of the task. It previously moved under the task description, causing the interface to split the comment content unnaturally. The comment section now renders after other content and before the top bar, keeping comments at the bottom of the page as expected (HTPR-6955).

Fix A shared comment link now opens on that comment instead of the ticket top, with the comment visible on screen on both desktop and mobile. The link scrolls directly to the referenced comment when you open it—for example, from Slack or email—making it easier to reference specific points in a conversation. This fix improves navigation for long threads with hundreds of comments and helps ticket descriptions stay readable even on narrow phones (https://app.hypertask.ai/detail/project-15/7090).

Common actions include:

  • Back: Navigate back to the board using the ← Back to task button.
  • Move: Relocate the task to a different section, board, or project.
  • Duplicate: Create a copy with the same fields. When duplicating a task, the new task includes the full description and can be copied to another board in one step (see board-level Duplicate in the Boards & Sections docs).
  • Archive: Hide the task from current views while keeping it in the archive.
  • Delete: Permanently remove the task. Undo appears on the notification after deletion, clicking Undo restores the task to its previous column and keeps it available for future edits. For bulk deletions, undo restores all affected tasks together and still works with Ctrl / Cmd+Z.

Fix Opening a ticket now downloads its details once, and board cards stay up to date. Before this fix, opening a task from the board or by its link would trigger 2 to 3 redundant data fetches. (HTPR-7009).

Fix On mobile, tapping a board card no longer loads the task page twice. The board now shows the task without redundant data fetches, eliminating a flash or stutter that previously occurred. This fix applies across all boards and resizes, keeping the board-tap experience smooth. (HTPR-7105).

Security Tasks can link to GitHub pull requests. Board 15 now accepts automatic PR updates only from three known GitHub accounts: Valentin Yeo and two others configured by the board team, preventing outsiders from creating tasks, moving them to review, or commenting via PRs.

Security A person who is not on a board can no longer add labels to it or modify label assignments on tasks. Outsiders now receive a Forbidden error, while board members continue to manage labels as before.

Security A team-only share link no longer exposes task content to outsiders. Before, the page sent the whole task and comments to unauthenticated users who only saw blurred content. Now an outsider sees an empty page with a Sign in or Login bar and cannot see task details or comments.

Security When you attempt to move or nest a task under another task on an inaccessible board, the operation is refused and nothing is saved. Hypertask validates board boundaries before allowing parent-child relationships across unrelated teams, preventing accidental exposure of foreign task titles or context (HTPR-7167).

Create relationships between tasks to surface context without leaving tasks:

  • Block: Mark a task as blocking another task.
  • Blocked by: Identify what indirectly holds a task back.
  • Duplicate: Link to other tasks that represent the same work item.
  • Workers: Associate an agent or intelligent agent with the task for scheduling and coordination.

See a task's relations in the Relations section of the task detail view.

Break down a task into smaller units. Subtasks appear in the task detail under the Subtasks section. Mark them complete to show progress toward the parent task.

The task detail sidebar includes a rail of properties (title, priority, assignees, labels, etc.). The rail now occupies the full remaining dynamic viewport height, so it uses all available space rather than a fixed maximum and leaves no unused viewport space.

Task properties no longer scroll with the task thread, keeping them pinned to the sidebar for easy access while browsing comments and history.

When another browser, the CLI, or an agent changes a task, its open detail page refreshes the title, assignees, labels, priority, dates, status, attachments, and linked pull requests without a reload. If the live connection is unavailable, the page checks for changes every 10 seconds.

Track work hours on tasks via the Times section:

  • B opens the time entry modal from the task, or use the command palette ("Log time").
  • Manual per-day rows let you log time for any calendar day without a timer.
  • Export time logs as CSV for payroll or reporting.

See the Time Tracking guide for full details.

The AI Task Writer is a prompt-based task creation flow that generates complete, shippable tickets from paste inputs.

The Task Writer writes tasks in your team's style. It uses board-aware prompts, pulls task templates from boards, and uses search to find related tickets instead of inventing them.

  • From a board: Ctrl+J / Cmd+J and select Create with AI — Task Writer.
  • From the command palette: Ctrl+K — search for "Task Write" and select it.
  • From a task: Click the AI icon in the task header and select Task Writer.

After the Task Writer generates a draft, you can refine it just like any other AI-generated comment or description.

New Tickets now load instantly from cached board data, with no spinner, no "Loading..." text, and no placeholder animation. The entire opening experience is fast and lag-free across desktop and mobile.

  • Click to open: When you tap or click a task, it appears in about 0.15 to 0.3 seconds on both desktop and mobile.
  • No loading animation: No full-screen spinner, no pulsing grey bars, no brief placeholder state.
  • Suggested questions right away: If the AI panel is open, suggested questions appear immediately—not waiting for the API response.

The browser back and forward buttons now behave consistently with the app:

  • Press Back to return to the board. The board remains loaded and you can stay there.
  • Press Forward to re-open the last ticket you viewed.

This lets you browse through tasks inside the app while the rest of your session stays tight and fast.

  • Median open times are ~0.15 seconds on desktop and ~0.17 seconds on mobile.
  • The first open after a board loads takes about 0.25 to 0.33 seconds; subsequent opens are closer to 0.13 to 0.18 seconds.
  • The first open after a board loads now paints its cached title and description before expensive editing property controls, so the title and description appear instantly while controls like assignees, status, and priority still warm. This tighter paint-first sequence reduces the first-open delta to about 0.10 seconds—considerably faster than before (HTPR-6855).

Fix Ticket pages no longer shift or jitter after opening. Visual elements that previously filled in after the initial paint now appear instantly as part of the cached board data, keeping the title, description, and controls in place across desktop and mobile for all test accounts (HTPR-6899). (HTPR-6955).

We recommend using keyboard shortcuts to navigate:

  • Ctrl+J / Cmd+J to jump to a task or open it with the Task Writer.
  • Ctrl+O / Cmd+O to jump to a task or link from within the task detail.

These shortcuts preserve the instant-open feel and keep you moving without page spins or wait states.

Improvement When you assign a task from the assign picker, closing the picker or pressing Escape no longer drops the assignment. The human assignee name stays on the task and persists across page reloads and subsequent checks. This applies whether you assign from the board card or from a direct task link. (HTPR-6962).

Improved Pressing Back after opening a subtask now shows the parent task immediately instead of the subtask, with no "Loading..." flash, and Forward returns you to the subtask if needed. Opening a task directly from cached data shows it reliably within about 0.3 seconds on both desktop and mobile, eliminating previous delays. (HTPR-7004).

Improved Using J or the arrow keys to move to the next Inbox item now loads and displays it within about 0.3 seconds on desktop and mobile, removing lag that previously held up the wrong ticket title for up to several seconds. (HTPR-7001).

No flash of the ticket title after opening a board card

Section titled “No flash of the ticket title after opening a board card”

Fixed Pressing Back right after opening a board card now shows the board immediately, with no flash of the ticket title. In at least 19 of 20 quick Backs (within 0.3 seconds of opening a card), you see only the board, not the ticket, and the board is visible within 1 second. (HTPR-7003).

Fix Opening a ticket now downloads its details once, and board cards stay up to date. Before this fix, opening a task from the board or by its link would trigger 2 to 3 redundant data fetches. (HTPR-7009). See also https://app.hypertask.ai/detail/project-15/7104 for the original pipeline issue that triggered redundant page loads.

Fix On mobile, tapping a board card no longer loads the task page twice. The board now shows the task without redundant data fetches, eliminating a flash or stutter that previously occurred. This fix applies across all boards and resizes, keeping the board-tap experience smooth. (HTPR-7105).

Improved Opening a task on a cold phone with no cached data now shows its title and description sooner (11.8 s vs 14.1 s median, 95th-percentile gap of ~2.3 s). The first load paints the title and description earlier, while controls like assignee and priority still warm up afterward, keeping the experience instant and frictionless. (HTPR-7091).

Fix The ticket page no longer jumps on first load. The comment box appears once and never moves: 20 of 20 fresh loads on two test accounts, on both desktop and phone. Visual elements that previously filled in after the initial paint now appear immediately as part of the cached board data, keeping the title, description, and controls in place across platforms for all test accounts. (HTPR-7074).

Behavior change The comment box and comment thread no longer shift downward as content loads, so the task layout stays consistent across desktop and mobile from open to load. (HTPR-7132).

New Clicking a board card now initializes the task with a single board interaction instead of triggering redundant rendering. This keeps the opening experience snappy across desktop and mobile, especially after boards have already been reloaded.

Loading address-bar updates that occur as part of the navigation are tracked correctly as navigations within the same page rather than distinct page loads. The change applies across all boards and view types—Kanban, table, and card lists—with consistent, performant behavior. (HTPR-7104).

Improved Pages that use invite links now validate board context before sending requests. My Tasks and Inbox no longer fire invite-link requests without an associated board, which previously caused console errors for unmatched requests. With this fix, such invalid requests now surface a clear, user-facing message instead of a server error, keeping the console clean and providing explicit feedback when a board context is required.