Integration · Issue tracking
On roadmap — not yet shippedClarityLift + Jira
Jira issue-comment signals for engineering and operations team friction. Roadmap — not yet shipped.
Signals derived from Jira
Team friction (issue-comment tone)
Communication health (response times on assigned issues)
Silence (queue stall)
OAuth scopes ClarityLift requests
Every scope below has a documented purpose tied to a specific step in the data flow. ClarityLift never requests scopes it does not use.
read:jira-work
Read issues and comments
read:jira-user
Resolve users for the consent gate
Data flow, end to end
- 1Site admin installs the ClarityLift Jira app from the Atlassian Marketplace.
- 2Admin selects which projects to connect (default: none).
- 3Jira delivers comment events via webhook.
- 4Same DM gate (n/a — Jira has no DMs), consent gate, and aggregate-signal path.
What ClarityLift does NOT read on Jira
The privacy posture is led by what is excluded, not what is included.
- Direct messages between individuals — never read, ever.
- Group DMs — out of scope by design.
- Channel content from teams below the 10-member group floor.
- Personal account content of any kind.
- Issue body content (only comment threads, where the conversational signal lives).
- Customer-portal-facing service-desk content (PII risk too high).
- Worklog text — out of scope.
- Attachments and file content.
Retention
No comment text is persisted. Aggregate signals only.
Privacy considerations specific to Jira
- Jira Service Management projects are excluded by default — they typically contain customer PII.
- Atlassian Marketplace data residency selections (US, EU, AU) flow through; ClarityLift respects the customer’s declared region.
What the customer does at install time
- 1.Site admin installs the Marketplace app.
- 2.Admin selects projects to connect.
- 3.Admin maps projects to internal teams.