Skip to content

What's new

What shipped, and when.

A dated record of workspace surfaces. Sample preview titles on this site stay English.

Dates mark when these surfaces were in the product as described here.

  1. September 2026

    Workspace surfaces beyond the board

    • Mindmap of the same hierarchy

      Organization → department → project → list → task as a map. Those nodes are the same records, not a second plan kept beside the backlog.

    • Project knowledge base

      A wiki tree and published articles live in the project. Knowledge is not only a note attached to one task.

    • Dashboards you assemble

      Widget grids — KPIs, velocity, load — sit beside reports. The Sprint 18 burndown snapshot is not the only reporting surface.

    • Intake forms onto a list

      A public form maps a request onto a project list. Operations queues do not have to start as a forwarded email.

    • Fields stay live while others edit

      Assignees, dates, and text on a task update for people already looking at the item. If you go offline, those edits queue and apply when you reconnect.

    • Settings hub

      Statuses, custom fields, workflow rules, roles, Git, and card designer sit in one project settings grid — not a scavenger hunt across menus.

    • Shared task lists

      Share a list with a viewer, commenter, or guest without opening every project surface. The link is granted access, not a public internet board.

  2. August 2026

    Card chrome you choose

    • Card designer

      Projects decide which fields appear on board cards — keys, Git, remaining hours, custom fields — so the card matches how the team actually works.

  3. March 2026

    The planning model this site already describes

    • Three nested subtask levels

      Root at depth 0. Three levels below. The product rejects a fourth on create and on reparent — the UI does not invent extra depth.

    • One task, every view

      List, board, roadmap, calendar, sprints, and releases read the same tasks. TASK-101 is not copied between tools.

    • Organization, department, then project

      Project-scoped roles (admin, member, limited member, guest). Sessions and the permission matrix live with the product service.

    • GitHub and GitLab on the task

      Pull requests, branches, and checks sit on the item. Administrators own credentials on the backend.

    • Five product locales

      English, Arabic (RTL), French, Portuguese, and Italian in the workspace — the same set as this marketing site.

Open a workspace and see the surfaces.

Get started if your organization allows registration, or sign in to a project you already have.