Skip to Content
IntegrationIntegrations

🔗 Integrations

Connect Sniffer with Jira, GitHub, Slack, Zendesk, Azure, AWS, and CRM tools — 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, Bitbucket, S3, and CRMs extend Sniffer into code management, team communication, customer support, attachment storage, and contact enrichment.

Integrations are configured at two levels:

  • Company-level — Set in Company Settings → Integration. 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 → Integration to configure organization-wide credentials.

📂 Integration Categories#

CategoryIntegrations
☁️ Cloud ProvidersAWS CodeCommit, API Gateway
📇 Contact InformationSalesforce, HubSpot, Microsoft Dynamics
📁 File StorageBox.com, Google Drive, Amazon S3
🎫 Ticket ManagementJira, Jira Service Desk, Zendesk
🔔 NotificationsSlack, Microsoft Teams
💻 Code RepositoryGitHub, Bitbucket
🤖 AI / LLMOpenAI, Anthropic, Azure OpenAI (for AI features)

🃏 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 badge — “Configured Successfully” or “Configure Now”
  • Last Tested — timestamp of last connection test

📝 Connection Credentials#

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

IntegrationRequired Fields
JirajiraUsername, jiraPassword (API token), jiraHost
Zendesksubdomain, email, apiToken
GitHubgithubAuth (personal access token), repoOwner
BitbucketbitbucketAuth, repoOwner
Azure DevOpsorganization, personalAccessToken
AWS CodeCommitcodeCommitUsername, codeCommitPassword, awsAccessKeyId, awsSecretAccessKey, region
API GatewayawsAccessKeyId, awsSecretAccessKey, region
SlackchannelId, token (or full OAuth flow)
Microsoft TeamstenantId, clientId, clientSecret, channelId
S3region, accessKeyId, secretAccessKey, bucket
SalesforceuserName, password, securityToken
HubSpotapiKey
Microsoft DynamicstenantId, clientId, clientSecret, environmentUrl
OpenAI / AnthropicapiKey, optional baseUrl, model

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

🧪 Test Connection#

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

📋 Project-Level Integrations#

Navigate to Settings → Integrations within any project (/sf/projects/:id/settings/integrations).

🖼️ Insert image of the Project Settings → Integrations tile grid.

🔧 Available Integration Tiles#

GroupIntegrationsStatus
📋 Project ManagementJira ✅, Jira Service Desk ✅, PMO Hub ✅Active
💬 CommunicationSlack ✅, Microsoft Teams ✅Active
🎧 HelpdeskZendesk ✅Active
📇 CRMSalesforce ✅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 FieldJira FieldNotes
StatusStatusMap each Sniffer status to a Jira status
PriorityPriorityMap priority levels
Issue TypeIssue TypeBug, Task, Story, etc.
AssigneeAssigneeMap Sniffer users to Jira users (email → account ID)
SeverityCustomOptional — map to a Jira custom field
Tags / LabelsLabelsSniffer tags become Jira labels
Story PointsCustomOptional — map to story points custom field

⚙️ Sync Toggles#

ToggleDescription
Auto-Create Jira TicketAutomatically create a Jira issue when a bug is created in Sniffer
Sync To JiraPush status/field changes from Sniffer to Jira
Sync From JiraPull status/field changes from Jira to Sniffer
Sync Comments To JiraPush comments from Sniffer to Jira
Sync Comments From JiraPull comments from Jira to Sniffer
Sync AttachmentsPush screenshots/recordings as Jira attachments
Assign to Our PortalMap Jira portal users to Sniffer members
Two-Way Resolution SyncMirror resolution states

📊 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:

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

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


🔔 Slack Configuration#

When connected to a project, Slack sends notifications for:

  • New bugs / tickets
  • Status changes (configurable)
  • Comments and @mentions
  • Live Logs / System Bug alerts
  • Feedback path rule triggers

Channel selection happens at the project level using a multi-select of Slack channels available to the bot.


🧩 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.


🤖 MCP (Model Context Protocol)#

Sniffer also exposes its data to AI coding assistants via MCP. See 🤖 MCP Integration → .


🔐 Permissions#

ActionRequired Permission
📋 View integrationsINTEGRATIONS.VIEW
⚙️ Configure integrationsINTEGRATIONS.CONFIGURE
🧪 Test connectionsINTEGRATIONS.TEST
🗑️ Remove configurationsINTEGRATIONS.DELETE

TopicDescription
🧩 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
🔌 Browser Extension → Jira / Azure RCA sidebar from the extension
🏢 Company Settings → Where company-level credentials live
⚙️ Settings → Project-level integration management
💬 Feedback → Route feedback to connected tools
🤖 MCP Integration → AI assistant access to Sniffer data

© 2026 Your Company