🔗 Integrations

Connect Sniffer with Jira, GitHub, Slack, Zendesk, Azure, and more — with two-way sync, field mapping, and automated workflows.

🌟 Overview

Sniffer integrates with the tools your team already uses. The centerpiece is Jira Cloud — full two-way synchronization of issues, statuses, comments, and fields. Additional integrations with GitHub, Slack, Zendesk, Azure, and Bitbucket extend Sniffer into code management, team communication, and customer support.

Integrations are configured at two levels:

Company-level — Set in Company Settings → Integrations. Shared credentials used as defaults across all projects.
Project-level — Set in each project’s Settings → Integrations. Choose which Jira project, Slack channel, or repository links to this specific project.

Once configured, integrations work automatically. Issues created in Sniffer appear in Jira without manual intervention. Changes propagate bidirectionally. See the 🧩 Sniffer for Jira app for viewing bug details inside Jira.

🏢 Company-Level Integrations

Navigate to Company Settings → Integrations to configure organization-wide credentials.

📂 Integration Categories

Category	Integrations
☁️ Cloud Providers	AWS CodeCommit, API Gateway
📇 Contact Information	Salesforce, HubSpot, Microsoft Dynamics
📁 File Storage	Box.com, Google Drive, Amazon S3
🎫 Ticket Management	Jira, Zendesk
🔔 Notifications	Slack
💻 Code Repository	GitHub, Bitbucket

🃏 Service Card UI

Each integration shows as a card with:

Logo and integration name
Description of what it does
⚙️ Configure button — opens the connection drawer
▶️ Test Now button — tests the connection and shows success/failure
Status — “Configured Successfully” or “Configure Now”
Last Tested — timestamp of last connection test

📝 Connection Credentials

Click Configure to open the drawer. Fields vary by integration:

Integration	Required Fields
Jira	`jiraUsername`, `jiraPassword` (API token), `jiraHost`
Zendesk	`subdomain`, `email`, `apiToken`
GitHub	`githubAuth` (personal access token), `repoOwner`
Bitbucket	`bitbucketAuth`, `repoOwner`
Azure DevOps	`organization`, `personalAccessToken`
AWS CodeCommit	`codeCommitUsername`, `codeCommitPassword`, `awsAccessKeyId`, `awsSecretAccessKey`, `region`
API Gateway	`awsAccessKeyId`, `awsSecretAccessKey`, `region`
Slack	`channelId`, `token`
S3	`region`, `accessKeyId`, `secretAccessKey`, `bucket`
Salesforce	`userName`, `password`, `securityToken`
HubSpot	`apiKey`
Microsoft Dynamics	`tenantId`, `clientId`, `clientSecret`, `environmentUrl`

Note: Sensitive fields (API tokens, passwords) are masked with visibility toggle 👁️ and stored encrypted.

🧪 Test Connection

Click ▶️ Test Now on any configured integration
Confirm in the dialog: “Are you sure you want to Test?”
Result shows as a banner: ✅ “Test Success on [date]” or ❌ “Test Failed on [date]”

📋 Project-Level Integrations

Navigate to Settings → Integrations within any project.

🔧 Available Integration Tiles

Group	Integrations	Status
📋 Project Management	Jira ✅, Asana (coming soon), Azure Boards ✅	Active
💬 Communication	Slack (coming soon), Microsoft Teams (coming soon)	Coming Soon
🎧 Helpdesk	Zendesk ✅	Active

Click a tile to open the Integration Config Drawer.

🔄 Jira Configuration (Project-Level)

The Jira integration drawer contains:

📁 Project Mapping

Select the Jira project to sync with from a searchable dropdown. Sniffer fetches all projects from your connected Jira instance.

📊 Field Mapping Table

Map Sniffer fields to their Jira equivalents:

Sniffer Field	Jira Field	Notes
Status	Status	Map each Sniffer status to a Jira status
Priority	Priority	Map priority levels
Issue Type	Issue Type	Bug, Task, Story, etc.
Assignee	Assignee	Map Sniffer users to Jira users

⚙️ Sync Toggles

Toggle	Description
Auto-Create Jira Ticket	Automatically create a Jira issue when a bug is created in Sniffer
Sync To Jira	Push status/field changes from Sniffer to Jira
Sync From Jira	Pull status/field changes from Jira to Sniffer
Sync Comments To Jira	Push comments from Sniffer to Jira
Sync Comments From Jira	Pull comments from Jira to Sniffer
Assign to Our Portal	Map Jira portal users to Sniffer members

📊 Status Mapping

Map each Sniffer status column to its corresponding Jira status. For example:

Sniffer “Todo” → Jira “To Do”
Sniffer “In Progress” → Jira “In Progress”
Sniffer “Done” → Jira “Done”

🎧 Zendesk Configuration (Project-Level)

The Zendesk drawer shows:

State	What You See
Not configured at company level	”Configure Zendesk” button → navigates to Company Settings
Configured at company level	Info alert + toggle switch: “Connect this project to Zendesk”
Toggle ON	✅ Green confirmation: “Zendesk will be connected when you save”
Toggle OFF	Project disconnected from Zendesk

When connected, bugs created in this project automatically create Zendesk tickets with bidirectional sync.

🧩 Sniffer for Jira App

In addition to API-level sync, Sniffer provides a Forge-powered Jira app that adds a panel inside Jira’s issue sidebar. This panel shows full bug context — screenshots, recordings, console/network logs, AI analysis — without leaving Jira.

See 🧩 Sniffer for Jira → for full details.

🔐 Permissions

Action	Required Permission
📋 View integrations	`INTEGRATIONS.VIEW`
⚙️ Configure integrations	`INTEGRATIONS.CONFIGURE`
🧪 Test connections	`INTEGRATIONS.TEST`
🗑️ Remove configurations	`INTEGRATIONS.DELETE`

Topic	Description
🧩 Sniffer for Jira →	The Forge app that brings bug context into Jira
📋 Task Board →	Issues sync between the board and Jira
📁 Projects →	Configure integrations during project creation
⚙️ Settings →	Project-level integration management
💬 Feedback →	Route feedback to connected tools