Changelog

Real-time inbox

New @mentions appear in your inbox the moment they land — no page reload, no polling delay. Push notifications replace the previous scheduled refresh entirely, so your inbox reflects reality at all times.

SQL storage — ~50% faster inbox load

Action items are now stored in a relational database. Dashboard counts now reflect your entire dataset, not just the loaded page.

Urgency accuracy: 96%

The AI classification now uses additional context signals for more accurate urgency and impact decisions. Validated accuracy: 96%.

Overdue items always display as CRITICAL

Items with an overdue deadline now always display as CRITICAL at render time, regardless of the stored urgency level. This bridges the window between when the deadline passes and the next scheduled escalation.

Due date auto-escalation

Items within 3 days of their Jira due date now escalate urgency correctly even when the comment text contains no deadline keywords. Previously, escalation only triggered if the comment explicitly referenced the deadline.

Self-mention filter

Your own @mentions no longer appear in your inbox. This is now enforced consistently across Jira, Confluence, and JSM.

WHY tooltip redesigned

The classification explanation now shows three sections: what to do, who is affected, and which signals drove the classification. The urgency badge gets its own separate tooltip showing what was evaluated.

Card expand/collapse

When a comment body is truncated, a compact expand/collapse button appears in the badge row. Click it to expand the full comment inline without opening the issue.

Groups default state

A new setting in Settings → Default View lets you choose whether the grouped inbox starts expanded or collapsed on load. The default is expanded.

Filter count consistency

Dashboard card numbers now always match the count in the filtered list when clicked. Counts are consistent across all dataset sizes.

Bug fixes

• Fixed: "Go to comment" deep-link was replaced with the issue URL when a Jira comment was edited.
• Fixed: dark theme — banner gradient, active button selection, and settings modal styling.
• Fixed: Confluence mentions now use the same intelligent model selection as Jira. Previously always defaulted to the faster model.
• Fixed: Confluence items incorrectly appeared when searching a Jira issue key in the inbox.
• Fixed: muted Confluence projects showed raw space IDs instead of display names.
• GDPR: "Unlimited" data retention removed. Maximum is now 365 days.

Runs on Atlassian

All AI classification now runs inside Atlassian's own infrastructure using Forge LLMs. No data leaves your Atlassian cloud for AI processing. This qualifies the app for the Runs on Atlassian badge — the highest trust tier on the Atlassian Marketplace. No external API calls are made.

Confluence page and Jira issue description mentions

@mentions in Confluence page bodies and Jira issue descriptions are now detected and classified — not just comments. If someone @mentions you in a page, a blog post, or a Jira issue description, it appears in your inbox with full 3D classification.

Deadline-aware urgency

40+ deadline phrases are now detected automatically — EOD, COB, ASAP, end of sprint, before the release, by Friday, end of Q3, and more. When a phrase is detected, the deadline is extracted and displayed as a badge (⚠ Due in 4 days). Urgency escalates automatically as the date approaches — items within 2–3 days escalate to High, items within 24 hours escalate to Critical. A live countdown appears in the urgency tooltip. No manual flagging needed.

Rich comment rendering

Comment bodies now render with full formatting — headings, bullet lists, code blocks, tables, panels, task lists, decision lists, and Confluence macros. Comments show in full with a Read more / Show less toggle.

Multi-mention cards

When you are @mentioned multiple times within a single Jira issue or Confluence page, all mentions are grouped into one card. Each mention block is independently resolvable.

Edited mention detection

If a comment or issue description containing your @mention is edited, the classification updates to reflect the new content. Edits that change the meaning trigger reclassification.

Smarter AI classification

Three accuracy improvements: (1) Context enrichment — the AI now receives the issue's due date, fix versions, labels, assignee, and a normalised priority signal to inform urgency and impact decisions. (2) Recipient role — whether you are the sole recipient, the assignee, a primary recipient, or one of multiple co-recipients is computed and passed to the AI, reducing false Individual classifications on team-wide @mentions. (3) Source-aware model routing — Confluence and JSM mentions without priority route to the faster model; complex high-priority Jira issues route to the reasoning model.

Dashboard — Deadline tab

A new Deadline tab groups your inbox by time horizon: Today, Tomorrow, This Week, Next Week, This Sprint, and Overdue. Click any bucket to filter your inbox to exactly those items.

Dashboard — filter accuracy fix

Priority card counts and inbox filters now use deadline-adjusted urgency consistently. An item escalated from Normal to Critical by a deadline no longer appears in both counts simultaneously.

Admin config improvements

Monitoring status now reflects all three products (Jira, Confluence, JSM) rather than Jira only. The default on first install is monitor everything — no configuration needed to get started. Excluding a project or space now correctly stops those items from appearing in the inbox.

Confluence comment edit events

Edits to Confluence comments now trigger reclassification. Previously only new Confluence comments were detected.

Bug fixes

• Fixed: Confluence disconnect and reconnect from the admin config page was broken — reconnect now works without requiring a page reload.
• Fixed: "end of the sprint" and "end of the current sprint" deadline phrases were not matching.
• Fixed: relative deadline phrases (coming Monday, by Friday) were resolving inconsistently depending on when the classifier ran — they now resolve relative to when the comment was written.