Imports bring custom fields across

• monday.com: columns that aren't the item's status, priority, owner, dates or tags become the project's custom fields: another status column (a select), dropdowns (multi-select), numbers (money when the unit is a currency), people, dates, checkboxes, links, ratings and text. Columns with no field of their kind (formulas, mirrors, connections) stay listed in the task's description, as before.
• Asana: each project's custom fields, with every task's values. A field called Priority still becomes the priority; a formula's value, worked out by Asana, goes into the task's description.
• ClickUp: dropdowns, labels, numbers, money in any currency ClickUp names, dates, checkboxes, links, people, ratings and text.
• Notion: a database's other properties become fields; a multi-select called Tags or Labels becomes the task's tags (it used to bring every multi-select as Property:Option labels).
• Trello: fields from the Custom Fields power-up.
• Jira: a custom field comes across once an issue in the project has a value for it (selects, checkboxes, labels, numbers and story points, text, links, dates, people).
• Options keep their colours. A field that's already in the project (an earlier import of the same workspace, or one made by hand) is used rather than doubled; two of a source's fields with one name stay two.
• A value no field can keep (a project at its 30 fields, an option past 50, a person who wasn't imported, a link that isn't one) is written into the task's description under Imported fields, as the source showed it, and the import's Errors say why, once per field.
• Roll back takes away the fields an import made, unless a task someone added since uses one.

A faster first screen

• The app's first screen no longer downloads the rich-text editor (ProseMirror, Yjs, code highlighting), the realtime client or an animation library: about 40% less code before Home shows on the demo. Thread, task and AI panels load the first time they open, and in the background once the app is idle.
• The API connection is warmed while the page loads, and the sign-in screen asks for its options beside the session check instead of after it.