AI Comment Action Inbox (ACAI) for Jira — by Sivect
Sivect ACAI · AI Comment Action Inbox for Jira
ACAI — Sivect's AI Comment Action Inbox — is a Forge-native app that captures every @mention across Jira, Jira Service Management, and Confluence, classifies each one with AI across three dimensions, and surfaces them in a prioritised personal inbox so nothing falls through the cracks.
Researchers identified this exact failure mode in 2003 — work lost because the communication channel and the task-management layer were separate systems. AI Comment Action Inbox unifies them.
— Bellotti et al. · ACM CHI 2003
@you release checks all green in staging. Waiting for your approval to proceed with prod deployment.
@you need your formal headcount request by COB — Finance closes Q3 budget tomorrow morning.
Typical response
Knowledge workers context-switch every 3 minutes across 10 working spheres per day. Classifications are ready before you return.
— Mark, Gonzalez & Harris · ACM CHI 2005
Architecture — GDPR Art. 25
Zero raw user data reaches the AI
— Cavoukian · Privacy by Design, 2009
Auto data eviction
Action items automatically cleaned up
New items surface between tasks — not during them.
— Iqbal & Bailey · ACM CHI 2006
The Product
3D AI Classification
Every @mention classified across three independent dimensions simultaneously: Action (RESPOND, REVIEW, APPROVE, FIX, BUILD, WATCH, NOTE), Urgency (CRITICAL, HIGH, NORMAL, LOW with timeframe context), and Impact (CUSTOMER, REVENUE, TEAM, INDIVIDUAL). Not a single score — a full picture.
In Detail
Action, Urgency, and Impact — visible at a glance.
Every @mention gets a three-dimensional classification — so you know exactly what to do, how fast, and who it affects.
Why three dimensions? Urgency and Impact map directly to the Eisenhower Matrix — the prioritisation framework engineering teams already know. The Action dimension is the layer the Eisenhower Matrix never had: RESPOND · REVIEW · APPROVE · FIX · BUILD · WATCH · NOTE. It answers not just when to act, but exactly what kind of action is required. This combination does not exist natively in Jira or anywhere else in the Atlassian ecosystem.
Urgency × Impact: Eisenhower Matrix · Action dimension: Bellotti et al., ACM CHI 2003
Personal Priority Inbox
All @mentions from Jira, Jira Service Management, and Confluence in one unified inbox. Critical items surfaced first. Unread tracking, resolve with 10-second undo window, and bulk resolve for processing multiple items at once.
Dashboard to Classification
Drill from a high-level dashboard view straight into the underlying classified items. Click any priority, urgency, or impact bucket to see exactly which @mentions sit behind it — context preserved, filters auto-applied.
Admin Configuration
Jira admins control which Jira projects, Jira Service Management projects, and Confluence spaces are monitored. Include or exclude mode per product. Changes apply immediately across all users — no per-user configuration required.
Advanced Filtering & Search
Filter by Action type, Urgency, Impact, Project, Issue Type, Author, Time Range, Read Status, and Source. Full-text search. Stackable filter chips. All filters persist per user session.
Grouped Views
Switch between flat list, grouped by issue, or grouped by source (Jira / JSM / Confluence). Collapsible groups. View mode and sort order persisted per user.
Smart Auto-Refresh
Your inbox stays current automatically. A visual refresh indicator shows sync status at a glance, with manual refresh always available.
Mute Controls
Mute noisy projects or specific authors. Toggle muted item visibility without losing coverage. Cut through the noise while keeping full audit trail.
Storage Management
Monitor your inbox storage at a glance. Clear resolved items, older items, or reset entirely — all from within your user settings. Data older than 60 days is automatically evicted.
Grouped by Issue
When a hot ticket explodes, nothing gets missed.
A single Jira issue, Confluence page, or JSM ticket can rack up dozens of @mentions in minutes. AI Comment Action Inbox collapses every mention on that one item into a single thread — sorted by urgency, with CRITICAL items surfaced first — so the right people respond immediately without scrolling through comment history.
- 1
@mention detected
Forge trigger fires on Jira, Jira Service Management, or Confluence comment events. Zero mentions? Processing stops immediately — nothing stored.
- 2
Multi-layer PII sanitisation
Emails → [EMAIL]. Phone numbers → [PHONE]. API keys & tokens → [SECRET_N]. Account IDs → [USER_N]. Customer names → [CUSTOMER_N]. HR/legal terms → [SENSITIVE]. Credit cards → [CREDIT_CARD]. Personal name signatures → [NAME]. Sanitised text only proceeds to AI.
- 3
AI classification
Sanitised text and basic issue context (title, type, priority, status) are sent to Anthropic Claude. The response is validated and post-processed before reaching your inbox.
- 4
Near-instant delivery
Classifications typically surface in your inbox in under 100ms, ready to triage.
- 5
Resolve, mute, or act
Resolve in one click, mute noisy authors, or jump straight to the source comment in Jira, JSM, or Confluence.
Intelligence Layer
See your workload differently.
The Urgency × Impact matrix gives you an instant read on where pressure is building across your team — before it becomes a crisis. Click any cell to filter your inbox to exactly those items.
Your data never leaves Atlassian infrastructure.
AI Comment Action Inbox is built entirely on Atlassian Forge — Atlassian's own serverless platform. All data is stored exclusively in Forge Storage (Atlassian's encrypted key-value store). There is no external database. There are no external servers. The only external call made by this app is to the Anthropic API for AI classification — and only PII-sanitised text is sent. Raw comment text, user account IDs, email addresses, and all other identifiable information are replaced with typed tokens before leaving your Atlassian instance.
Permissions requested — and why.
AI Comment Action Inbox requests only the permissions it actively uses. Here is every permission and exactly why it is needed.
read:jira-workRead Jira issue details, comments, and attachments when an @mention is detectedread:jira-userRead author display names for inbox renderingstorage:appRead and write to Forge Storage (your personal inbox data)read:confluence-content.summaryDetect Confluence comment eventsread:content:confluenceRead Confluence comment body textread:comment:confluenceRead Confluence comment metadataread:space:confluenceRead Confluence space information for admin configurationread:page:confluenceRead Confluence page context for comment displayread:user:confluenceRead Confluence author display namesread:servicedesk:jira-service-managementAuto-detect JSM projects for admin configurationEvery design decision maps to published research.
AI Comment Action Inbox was not designed by guesswork. The problem, the classification model, the privacy architecture, and the AI pipeline each map to peer-reviewed research in human-computer interaction, cognitive science, and AI.
THE PROBLEM
In 1996, researchers identified that knowledge workers were using email as an accidental task manager — a communication tool pressed into service as a to-do list. In 2026, your team is doing the same thing with Jira comments.
Whittaker & Sidner · ACM CHI 1996 Bellotti et al. · ACM CHI 2003
THE COST
Knowledge workers average 3 minutes on a task before context-switching, across 10 working spheres per day. Interruptions don't just cost time — they degrade cognitive state, increasing stress and error rate. The inbox is the resumption aid this research implied was needed.
Mark, Gonzalez & Harris · ACM CHI 2005 Mark, Gudith & Klocke · ACM CHI 2008
THE DESIGN DECISION
Interruption cost is not constant — it depends on where in a task the interruption lands. Interruptions at subtask boundaries cost significantly less than mid-task interruptions. AI Comment Action Inbox batches new items on a set interval rather than pushing notifications in real-time. New items surface between tasks, not during them.
Iqbal & Bailey · ACM CHI 2006
THE FRAMEWORK
Urgency and Impact map directly to the Eisenhower Matrix — the most cited prioritisation framework in productivity research. The Action dimension (RESPOND · REVIEW · APPROVE · FIX · BUILD · WATCH · NOTE) is the novel extension: it answers what kind of action is required, not just when. This combination does not appear in prior published literature.
Eisenhower Matrix Bellotti et al. · ACM CHI 2003
PRIVACY
The 8-layer PII sanitisation pipeline is structural, not configurable. It runs before every AI call. This is Privacy by Design Principle 1 — Proactive not Reactive — now codified in GDPR Article 25. Raw comment data never reaches the AI.
Cavoukian · Privacy by Design, 2009 GDPR Article 25
THE AI
Classification uses chain-of-thought prompting with cross-industry few-shot examples — industry-neutral, covering healthcare, finance, legal, HR, engineering, and sales. Zero-shot generalisation means accurate classification across any team's Jira instance without fine-tuning.
Wei et al. · arXiv 2022 Sanh et al. · ICLR 2022 Ouyang et al. · NeurIPS 2022
The researchers and institutions cited above have not reviewed or endorsed this product. Citations reflect published findings that are consistent with the design decisions made independently in building AI Comment Action Inbox.