Version 1.216.85 Release Note
Since 1.190.85, AB Projects spent most of its energy on the small bumps you don’t notice until they’re fixed: “my tasks” finds your tasks again, subtask editing actually opens the subtask, the bot greets people who don’t yet have an AB Projects account instead of falling silent, and a handful of links stopped sending you to 404s. CRM-linked projects also got a few quality bumps that make jumping between project work and CRM context less of a context switch.
“My Tasks” Finds Your Tasks Again
- Project owners no longer see empty bot responses. A few project owners reported “my tasks” and “tasks today” coming back empty even though they clearly had work assigned. Root cause: a soft-delete bug had left multiple identity rows sharing the same Teams user ID, and the lookup landed on the wrong (deleted) row. Deletion now clears Teams identifiers, a filtered unique index protects against duplicates, and the lookup explicitly skips soft-deleted users.
- The bot’s task cards render correctly when populated. A regression in the two-table card builder was making the “due today” and “starting today” sections silently render empty even when they had rows. Fixed — the populated rows now show up as expected.
Subtasks Are Now First-Class
A wave of small bugs in the subtask experience — editing, commenting, opening from the slide panel — shared a root cause: HTML element IDs (for the edit panel, the Quill rich-text editor, and the comment editor) were duplicated across every task on the page. The first task on a screen worked fine; everything nested underneath broke in subtle ways. All cleaned up:
- Edit panels open the right subtask. Clicking Edit on a subtask used to silently open the parent task’s edit panel, or do nothing at all. Now every panel is scoped to its own task and behaves as expected.
- Comment editors stay separate. The comment editor on a subtask no longer borrows the parent task’s editor state — you can comment on a subtask without seeing it appear under the parent.
- Subtask detail opens from anywhere. Clicking a subtask in the slide-out panel now properly forwards the project and user context, so the detail view loads the right data.
- Task IDs with hyphens work in JavaScript handlers. An eval-based event handler couldn’t see object keys that contained hyphens (which our task IDs do). Switched to bracket notation; subtask handlers find their tasks correctly now.
Friendlier First Run from the Bot
- New users get a clear onboarding prompt. When someone messages the bot from Teams but hasn’t yet opened the AB Projects tab in any channel, the bot now responds with a friendly “open the tab in any channel to get started” prompt — instead of an unhelpful “no tasks found” or a silent crash.
- Localized in all nine languages. The new prompt is translated into the same nine languages as the rest of the in-Teams experience — Arabic, Simplified Chinese, French, German, Japanese, Korean, Portuguese, Russian, and Spanish — so first-time users see it in their Teams language.
- Crashes notify the team. Unexpected bot exceptions now also email the dev team automatically, so problems get caught and fixed before they hit more users.
Sharper Web and Home-Tab Navigation
- Overdue task links from the Home tab open the task. Clicking an overdue task in the Home tile used to land on a 404 because the route didn’t exist. Added the missing route; the tile is fully interactive again.
- Web Dashboard task links don’t bounce. Clicking a task from the web Dashboard used to redirect to the home page in some sign-in states. The bouncing branch is gone — tasks open directly.
- Home tab three-dot menu doesn’t re-render the AI message. Opening the menu on a tile no longer briefly flashes a re-rendered AI message.
AI Disclosure
- In-app AI labels and a reporting link. Anywhere AB Projects generates content with AI (suggested titles, draft replies, summary text), the result is now visibly labelled as AI-generated, and a “Report content” link lets you flag anything that looks wrong. Required by Microsoft Teams App store review and good practice regardless.
CRM-Linked Project Polish
- Project / CRM / Logs tabs in the project header. Projects with a linked CRM now show all three tabs at the top — jumping between project work and CRM context no longer requires backing out to the projects list.
- Capability badges on the projects list. Each project now shows small badges for the capabilities it has linked (Project, CRM), so you can see at a glance which projects have CRM enabled.
- CRM button shows whenever a project has CRM linked. The button no longer depends on a per-user permission check — if the project has CRM, every member of the project can see it.
- Mail provider visible on the single-project view. The configured email provider now appears on the individual project page, matching what the projects list already showed.
- Lead refresh and click stability. Refreshing the leads list and clicking individual leads no longer occasionally freeze the page for CRM-licensed accounts.
Polish & Quality of Life
- Missing CMS articles return 404 instead of crashing. Visiting a missing article path now produces a clean 404 page rather than a null-reference exception — benefits anyone hitting older blog URLs.
As always, AB Projects updates automatically — nothing to install. If anything looks off after the new version lands for you, the team is only a message away.