Version 1.190.85 Release Note
Since 1.173.85, AB has gone through a rebranding pass to clear up Teams App Store confusion, lifted a long-standing storage limit on tasks and wiki articles, and added a few resilience improvements that show up most when something has already gone wrong. None of these are dramatic on their own — together they make the app feel lighter and harder to break.
A New Name: AB Projects
The Teams app is now AB Projects, replacing the previous "AB" name everywhere user-visible: the manifest, the welcome cards, the bot greeting in 1:1 and channel scopes, and the in-Teams localization for nine languages. The new name disambiguates from the rest of the AB family (AB CRM and friends) and avoids the "Tasks" framing — this is a tool for teams, not a personal to-do list.
- Eight new in-Teams locales. Arabic, Simplified Chinese, French, German, Korean, Portuguese, Russian, and Spanish join Japanese as fully-translated in-app experiences — manifest names, command titles, descriptions, and welcome cards all switch with your Teams language.
- Microsoft Teams brand alignment. Per Microsoft's brand guidelines, the first reference to Teams in the app listing now reads "Microsoft Teams" in every locale — visible in App Source listings.
- Bot greetings localized. The bot recognizes greetings and built-in commands like "my tasks", "team tasks", and "help" in nine localized forms (in addition to English).
Bigger Documents — No More 64 KB Limit
Wiki articles and task descriptions used to silently fail to save when their content crossed about 32,000 characters — Azure Table Storage's 64 KB-per-property cap. That ceiling is gone:
- Long wiki articles. Design docs, postmortems, multi-section tutorials — write them as long as you need. The body now lives in blob storage behind the scenes; the article record on the table side stays small with just a searchable preview.
- Long task descriptions. Same treatment for task descriptions. Pasting a multi-page brief into the description field no longer drops the SignalR connection mid-save.
- Search is preserved. A plain-text preview of every article and description is kept on the searchable record, so the filter and search experiences stay exactly as fast as before.
- Existing data keeps working. Articles and tasks saved before this change continue to display normally — the lookup falls back to the inline body when needed.
Smoother Subtasks
- Add Subtask panel always opens on top. When a task already had several subtasks, the embedded subtask list could trap the "Add Subtask" panel behind the task detail page — the panel was technically open but invisible. That's fixed: the panel floats on top now, and the embedded subtask list no longer competes for stacking.
- Due Date validation only flags invalid dates. The red border under the Due Date field used to appear on perfectly valid dates the moment the panel opened. The visual indicator was inverted in two places — both fixed. The red border now matches what you actually see.
- Long subtask descriptions save reliably. Pasting a long Quill-rendered description into the new subtask form no longer drops the SignalR connection before the save completes — the same SignalR ceiling fix that helps long task descriptions.
Sturdier Teams Notifications
- Auto-recovery when the parent message is gone. If someone deletes the original Teams message a task was anchored to, comments on that task used to silently fail to thread under the (now-missing) message. AB now detects the 404 and automatically posts a fresh card in the channel instead, so the activity stays visible. The task remembers the new card, so subsequent comments thread under it.
- Status, priority, and assignee changes get the same resilience. All the task-mutation panels share the same notification path — they all benefit from the recovery without any individual change.
Polish & Quality of Life
- Priority filter on the side search bar. Selecting High, Medium, or Low in the side search bar now actually filters by priority instead of returning all matches. Internally, every priority comparison across the codebase aligned to the canonical
1=High, 2=Medium, 3=Lowscheme — no more legacy numeric off-by-ones. - SQL connections retry transient failures. The web app, API, MCP, and function host now retry transient SQL failures automatically — brief connection blips no longer surface as user-visible errors.
- Edit panels click correctly again. A short-lived regression briefly placed a dark overlay over the edit panels after the subtask z-order fix shipped. Spotted the same day it was reported and rolled back — the overlay rule was over-broad and is gone.
As always, AB Projects updates automatically — nothing for you to install. If something looks off after the new version lands for you, the team is only a message away.