Jira
Status: Live
Required plan: Team Pro or Enterprise
The Jira integration automatically creates issues in your Jira project when feedback meets your configured trigger conditions. It supports Jira Cloud and connects via OAuth.
Setup
- Go to Settings → Integrations and click Connect on the Jira card.
- Click Authorize with Jira — you'll be redirected to Atlassian's OAuth flow.
- Grant access to your Jira workspace and you'll be redirected back.
- Select the Jira project where issues should be created.
- Choose the issue type (e.g. Bug, Task, Story).
- Configure your triggers (see below).
- Click Save.
Triggers
You control exactly which feedback creates a Jira issue. Triggers are evaluated in priority order — once one matches, no further checks run, preventing duplicate tickets.
| Trigger | Description |
|---|---|
| Serious concern | Creates a ticket when the AI flags feedback as a serious concern |
| Operational critical | Creates a ticket when feedback is marked operationally critical |
| Repeated feedback | Creates a ticket when the same theme is submitted N times within a time window |
| All feedback | Creates a ticket for every single submission |
Repeated feedback has two sub-settings:
- Threshold — how many matching submissions trigger a ticket (default: 3, range: 2–20)
- Window — the lookback period in days (default: 7, range: 1–30)
Priority mapping
Jira issue priority is auto-detected from the feedback's severity. You can customize the mapping:
| Feedback level | Default Jira priority |
|---|---|
| Critical | Highest |
| High | High |
| Medium | Medium |
| Low | Low |
You can also set a priority override to force all tickets to a single priority regardless of detection.
Epics
Jira tickets are automatically organized under epics — one epic per room. On the first ticket from a room, the integration searches for an existing epic named [Feedback] <room name> in your project and creates one if none exists. Subsequent tickets from the same room link to the same epic automatically. The epic key is saved back to the room so it persists across sessions.
Room-level overrides
Individual rooms can override the organization-level Jira configuration. Go to a room's settings and configure:
- Jira project key — route tickets from this room to a different project
- Jira epic key — link tickets to a specific existing epic
- Create tickets for all feedback — enable the all-feedback trigger for just this room, independent of the global trigger settings
Ticket content
Each Jira ticket includes:
- The feedback text (truncated if very long)
- The room name and event type
- The AI-generated sentiment label
- The trigger type that caused the ticket (e.g. "Serious Concern")
- A link back to the feedback in Anonfeedback
- AI reasoning (for serious concern tickets)
Custom prompt (Enterprise): Write a custom prompt that shapes how the AI summarizes and formats ticket descriptions. This lets you match your team's Jira conventions and include workflow-specific fields.
Custom trigger tags: Specify feedback tags that trigger ticket creation. If a submission includes any of these tags, a ticket is created regardless of sentiment or other trigger settings.
Viewing tickets
Click View tickets on the integration card to see all Jira tickets created from feedback, with links to the Jira issue and the original feedback item. The ticket count shown is sourced directly from the feedback database, not an internal counter.
Troubleshooting
| Problem | Fix |
|---|---|
| Status shows Auth failed | Click Reconnect to restart the OAuth flow — your token has expired or been revoked |
| Status shows Degraded | Check the last error on the card; common causes are an invalid project key or missing Jira permissions |
| Tickets created without an epic | The epic creation may have failed silently — check that your Jira project allows epics and the integration has create permissions |