A workspace that already has something in it

New

• Your first board comes with work on it: A new workspace used to open empty, on the one screen that is empty by definition for a new account. Signing up now lands you on a real board, in a project that already holds nine example tasks — each one showing something the board does: subtasks, labels, priorities, checklists, code blocks, connecting an AI agent. Delete them whenever you like. Every workspace also starts with six labels, so the label picker is no longer empty the first time you open it.
• The wait after signup shows what is happening: Creating a workspace takes a few seconds on the server. Instead of a blank screen, you now see a board assembling itself while it runs, and the real board fades in once its content is ready rather than over a set of skeletons.
• A short list of what to do first: A new workspace now gets a Getting Started card in the sidebar with the handful of things worth doing on day one — create a task, move one to another status, assign one, invite someone. It ticks items off from what you actually do rather than from clicking them, and it shows only the steps your role allows, so people joining an existing workspace by invitation get it too. Close it whenever you like; it leaves on its own once the list is done.

Improved

• Task updates reach your inbox and your email again: Changing a task’s title, description, due date, labels or cycle sent nothing at all — no email, no notification — even though the settings screen has had switches for both the whole time. Those switches now do what they say. The notification and the email name the fields that changed and show the old value struck through next to the new one, and the description is diffed word by word. A rewritten description is named rather than pasted in full.
• The digest email says what happened: When several things happen close together they arrive as one summary email. That summary listed only who touched what — “updated priority”, with no mention of which priority. Every row now carries the same detail as a single notification, including status and priority changes, which had the values available all along.
• Activity shows what changed, not just that something did: Editing a task’s description left a line in the activity feed that read “Changed description” and nothing else — the old and new text were recorded, just never shown. The feed now renders the change itself: removed words struck through, new words alongside them. Title changes read the same way, old title through, new one after it. Long untouched passages collapse to a few words of context so the edit stays easy to find, and a description rewritten from scratch says so rather than dumping two versions side by side.
• Due date changes read as dates: A due date change in the activity feed used to print the raw stored timestamp, so it said “from 2026-05-13T22:00:00.000Z to 2026-09-23T22:00:00.000Z”. It now shows the same date format as the rest of the app, and a date being added or cleared reads as such.
• Skipping the invite step is an actual option: The last step of onboarding asked you to invite your team with no clear way past it. Skip is visible now, and the sign-in options sit side by side rather than stacked.

Fixed

• Tasks no longer vanish or show up twice: Long lists are loaded a page at a time, and tasks with the same priority or creation time had no fixed order between those pages — so a task could arrive in two pages and another in none. The duplicate cards were the visible half of it; the missing tasks were the half nobody could see. This covered the board, My Tasks, the public share link and the Public API.
• Cycle progress stops moving backwards: A task counted as completed on the day it was last edited, not the day it was closed — so renaming or relabelling a finished task pushed it forward and a burndown chart could climb. Completion is recorded when it happens now.
• An interrupted signup no longer costs you the account: Reloading the page during “Creating your workspace” could leave the account half-created, with no way to finish or retry. The workspace now picks up where it left off.
• Deleting a project takes you back to your projects: Deleting a project dropped you onto a workspace that does not exist, so you landed on a broken page instead of the project list.
• Attachments delete through the Public API: Removing an attachment through the API did not go through.
• Your role comes back if a change fails: When changing a workspace member’s role failed partway, the member could be left with the wrong role instead of the one they started with.