Skip to Content
IntegrationSniffer for Jira

🧩 Sniffer for Jira

A Forge-powered panel inside Jira’s issue sidebar that displays full bug context — screenshots, recordings, console/network logs, device info, and AI analysis — without leaving Jira.


🌟 Overview#

Sniffer for Jira is an Atlassian Forge app that adds a “Sniffer” panel to the right sidebar of every Jira issue. When a Jira ticket was created by or synced with Sniffer, this panel lets your team view the complete bug context — including captured screenshots, screen recordings, console logs, network request data, device information, action timelines, and AI-powered analysis — directly inside Jira.

No more switching between tools. Engineers can see exactly what the user experienced, review diagnostic data, and understand root causes without leaving their Jira workflow.

🖼️ Insert image of a Jira issue with the Sniffer panel visible in the right sidebar.


📦 Installation#

  1. Install Sniffer for Jira from the Atlassian Marketplace .
  2. Grant the required permissions:
PermissionPurpose
read:jira-workRead Jira issue data to find linked bugs
write:jira-workAttach recordings and files to Jira issues
storage:appStore authentication sessions securely
read:jira-userMap Jira users to Sniffer assignees
  1. The “Sniffer” panel automatically appears in the right sidebar of every Jira issue.

🔑 Authentication#

The first time you open the Sniffer panel:

  1. Click “Sign in to Sniffer” in the panel.
  2. You are redirected to the Sniffer login page (Cognito OAuth).
  3. Enter your Sniffer credentials.
  4. After login, the session is stored in Forge Storage.
  5. Sessions last 30 days before requiring re-authentication.

Note: Each Jira user authenticates independently. Your session is tied to your Jira account ID.


🖥️ Issue Context Panel#

The Sniffer panel in the Jira issue sidebar has two states:

🔗 Bug Linked#

If a Sniffer bug is associated with this Jira issue:

  • A “View Preview” button appears with a thumbnail of the captured screenshot
  • Quick-glance metadata: severity, priority, reporter
  • Click to open the full Detail Modal (see below)
  • An “Unlink” button lets you remove the association

🖼️ Insert image of the panel in the “Bug Linked” state.

🔍 Bug Not Linked#

If no Sniffer bug is linked:

  • A search UI appears
  • Enter a bug key (e.g., SNF-142) or keyword in the text field
  • Click Search — results show bug key, summary, status badge, and a “Link” button
  • Click Link to associate the Sniffer bug with this Jira issue

📑 Detail Modal (5 Tabs)#

Click “View Preview” to open a full-screen modal with five tabs:

🖼️ Insert image of the Detail Modal with all 5 tabs in the header.

1. 📋 Overview Tab#

All bug metadata at a glance:

FieldDisplay
Bug Keye.g., SNF-142
SummaryBug title
DescriptionHTML-stripped description text
ProjectSniffer project name
StatusLozenge badge (color-coded)
SeverityHighest/High = 🔴 Red, Medium = 🟡 Yellow, Low = 🟢 Green
Issue TypeBUG, DEFECT, TASK, STORY, FEATURE, EPIC
AssigneesName badges
TagsTag labels
Page URLWhere the bug was reported
EstimationDays/hours/minutes
Start / Due DatesDate values
AttachmentsCount of attached files
FooterLast updated timestamp, reporter name and date

2. 🔍 Diagnostics Tab (conditional — shown only if logs/attachments exist)#

SectionDetails
📱 System InfoDevice brand, model, OS, browser
🎥 RecordingsLinks to video files (mp4, webm, mov, avi) with inline player
📟 Console LogsTable: Level, Message (truncated to 150 chars), Timestamp. First 30 entries. Color-coded: ❌ Error = red, ⚠️ Warn = yellow, default = gray
🌐 Network LogsTable: Method (GET/POST/etc.), URL (truncated to 120 chars), Status code. First 30 entries. Color-coded: 🔴 4xx+ = red, 🟡 3xx = yellow, 🟢 2xx = green
🖱️ Action LogsTable: Action type, Target element, Timestamp. First 30 entries

3. 💬 Comments Tab#

List of comments from the Sniffer bug:

  • Author name and timestamp for each comment
  • Plain text comment content (rich text rendered)
  • Shows “No comments yet” if empty

4. ⏱️ Work Logs Tab#

ColumnDescription
UserWho logged the time
DurationHours/minutes spent
DescriptionWhat work was done
DateWhen the work was performed

Shows “No work logs recorded” if empty.

5. 🤖 Bug Analyzer Tab (conditional — shown if project has analyzer enabled and issue is not an Epic)#

AI-powered defect analysis:

SectionDescription
Root CauseAI-identified likely cause
ImpactAssessment of affected users/features
SuggestionRecommended fix approach
Steps to ReproduceAI-generated reproduction steps
Analysis SummaryOverall narrative
CategoryClassification lozenge (UI, API, Performance, etc.)
ConfidenceHIGH 🟢, MEDIUM 🟡, or unspecified ⚪
Affected FilesList of likely source files involved

🎥 Recording Auto-Attach#

Sniffer can automatically attach screen recordings to Jira issues:

  1. From the Sniffer web app, generate a shareable recording link that includes the Jira issue key.
  2. After the recording is uploaded to S3, a webhook fires.
  3. The recording is auto-attached as a native Jira attachment.
  4. The attachment appears in Jira’s standard Attachments section, with a comment indicating it came from Sniffer.

🔌 Browser Extension Integration#

If you also install the 🔌 Browser Extension , an additional RCA sidebar appears on Jira bug detail pages — letting QA and engineers run an Ask-AI conversation right next to the Jira ticket and trigger Sniffer actions without opening the modal.


⚡ Performance#

FeatureDetails
CachingBug data cached in Forge Key-Value Storage (30-minute TTL)
Encrypted DataAPI responses decrypted using AES before display
Signed URLsScreenshot/attachment S3 keys resolved to signed URLs in bulk
Session ManagementAuth sessions persist for 30 days with version-based invalidation
Lazy loadingDiagnostics/Analyzer tabs only load their data when first opened

🐞 Troubleshooting#

SymptomLikely Cause / Fix
Panel never appearsConfirm the app is installed; refresh Jira
Panel stays in “Sign in” stateSession expired after 30d — click sign-in to re-auth
Linked bug shows “Not found”The bug was deleted in Sniffer, or you lack project view perms
Recording not auto-attachingVerify write:jira-work permission and webhook configuration
Bug Analyzer tab missingProject AI analyzer is disabled, or the issue is an Epic

See ❓ Troubleshooting →  for the full FAQ.


TopicDescription
🔗 Integrations → Set up Jira credentials and two-way sync
🐛 Bug Details → The same data shown in the Sniffer web app
🔌 Browser Extension → RCA sidebar inside Jira / Azure
📡 Live Logs → Auto-detected errors visible in Diagnostics tab
📋 Task Board → Issues that sync to Jira
🚀 Getting Started → Install Sniffer for Jira as Step 6

© 2026 Your Company