Ticket Intelligence Documentation

Administrator & User Guide · Team Tier · v1.0 · March 2026

Ticket Intelligence is an AI-powered incident intelligence platform built natively into Jira using Atlassian Forge.

Download Full Guide (.docx)

Overview

Ticket Intelligence Overview

Ticket Intelligence surfaces similar incidents, identifies subject matter experts, assembles incident war rooms, and generates AI-powered root cause analysis directly inside Jira.

Built on Atlassian Forge, Ticket Intelligence runs entirely within Atlassian infrastructure without requiring external application servers operated by the vendor.

Key Features

Quick Start

  1. Install Ticket Intelligence from the Atlassian Marketplace
  2. Open any Jira issue
  3. The Ticket Intelligence panel appears automatically
  4. Click RUN INTELLIGENCE ANALYSIS

Your organisation's ticket history is indexed automatically during the initial sync. Manual sync can be triggered via Settings → Sync now.

Ticket Intelligence Panel

Ticket Intelligence Panel

The Ticket Intelligence panel appears directly in the Jira issue view and automatically performs semantic matching against historical incidents.

Panel Capabilities

War Rooms

Slack and Teams War Rooms

Ticket Intelligence can automatically assemble private Slack or Microsoft Teams war rooms for P1/P2 incidents and invite identified domain experts.

Supported Integrations

Knowledge Graph

Knowledge Graph

The Knowledge Graph automatically maps expertise domains using historical issue resolution data.

The graph is intended for operational incident routing and collaboration, not employee performance evaluation.

AI Analysis

Running an intelligence analysis generates:

Data Sync

Ticket Intelligence performs automatic daily indexing of resolved Jira issues and optional Confluence content.

Indexed Content

Privacy & Security

Ticket Intelligence operates entirely on Atlassian Forge infrastructure. All credentials are stored encrypted using Atlassian Forge Storage.

External Services

No external integrations are used unless explicitly configured by the organisation administrator.

FinOps Controls

Administrators can configure daily API usage caps for:

Troubleshooting

Panel Not Appearing

Add the Ticket Intelligence panel via the Jira issue layout customisation menu (⚙).

No Matches Found

Trigger a manual sync and verify your Jira project contains resolved tickets.

Slack War Room Not Creating

Verify the Slack connector is connected and the bot has required scopes.

Knowledge Graph Empty

The graph populates after historical resolved issues are indexed.

Service Level Agreement (SLA)

Availability Target

Ticket Intelligence targets 99.5% monthly availability for core functionality, excluding scheduled maintenance windows, Atlassian platform outages, and third-party provider outages outside Ticket Intelligence control.

Core Functionality Covered

Third-Party Dependencies

Certain features depend on third-party providers including Atlassian Forge, OpenAI, Pinecone, Slack, Microsoft Teams, GitHub, GitLab, Datadog, Sentry, and Linear.

Support Response Targets

Severity Description Target Response Time
P1 Production outage or major functionality unavailable 4 business hours
P2 Major feature degraded but workaround exists 1 business day
P3 Minor issue or non-critical bug 3 business days
P4 Feature request or general enquiry 5 business days

Maintenance Windows

Scheduled maintenance may occur outside standard UTC business hours.

Support Contact

Email: help@unobtainableverge.com