Félix Malfait
9bdef449e6
## Summary Adds `upgrade:1-21:fix-message-thread-view-and-label-identifier` to retroactively apply two messageThread changes from #19351 that never propagated to existing workspaces (because `synchronizeTwentyStandardApplicationOrThrow` only runs at workspace creation): 1. **`allMessageThreads` view fields**: delete-and-recreate all view fields for the standard view from the current twenty-standard definition, which adds the new `subject` and `updatedAt` columns. Same pattern as the FIELDS_WIDGET sync in `1-21-workspace-command-1775500005000-backfill-page-layouts-and-fields-widget-view-fields`. 2. **`messageThread.labelIdentifierFieldMetadataId`**: repointed to the `subject` field via `validateBuildAndRunWorkspaceMigration`. The migration runner already resolves `labelIdentifierFieldMetadataUniversalIdentifier` → id in `update-object-action-handler`, so this goes through the standard flow and properly invalidates caches. Both fixes share a single `validateBuildAndRunWorkspaceMigration` call (one `viewField` op, one `objectMetadata` update op). Idempotent — skips if nothing to do. Depends on `upgrade:1-21:backfill-message-thread-subject` having run first (the label identifier fix needs the `subject` field to exist; it logs a warning and skips that part otherwise). ## Test plan - [ ] Legacy workspace: run \`backfill-message-thread-subject\`, then this command, then verify: - the \`allMessageThreads\` view shows the new \`subject\` and \`updatedAt\` columns - messageThread records display their \`subject\` as the record label - [ ] Re-run the command: no-op, logs \`Nothing to fix\` - [ ] \`--dry-run\` logs planned changes without applying them 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See: 🚀 Self-hosting 🖥️ Local Setup
Why Twenty
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Personalize layouts with filters, sort, group by, kanban and table views
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!