Throughput, mapped to your sprint — not just raw tickets.
Atlassian OAuth connects Jira Cloud in a click. Issue lifecycle events flow in via webhooks and story points roll up per person. We never read ticket descriptions, comments, or attachments.
Setup
Two steps. No IT ticket.
The Jira flow stays in OAuth-land. No agents on laptops, no bots to approve, no custom configuration per person.
- 1
Atlassian OAuth
Sign in with Atlassian, pick the Cloud site, and approve. Webhooks register automatically.
- 2
Map people to Jira accounts
Link each monitored person to their Atlassian account. Personal Data Reporting compliance is handled for you.
The trust contract
What WePeople reads from Jira.
Every scope is listed. Every refusal is listed. If it isn't here, we don't request it.
- Issue lifecycle events (created, in-progress, done)
- Story points per completed issue
- Issue keys and status transition timestamps
- Assignee account IDs (mapped to your monitored set)
- Issue descriptions or comments
- Custom field values
- Attachment contents
- Worklog comment bodies
What you get from Jira
Three signals, no busywork.
Everything below is assembled from Jira metadata alone.
Issue timeline
Every status transition becomes a timeline event. See the rhythm of 'in-progress' and 'done' overlaid with Slack presence and GitHub activity.
Story points throughput
Completed story points roll up per person and per team, period over period. A Performance signal with confidence, not a Jira leaderboard.
Weekly report · team
Week 14 (this week)- Ani Chen· SPACE score+0.8
- Juno Park· Effective time+12%
- Milo Fischer· Active time-15%
- Rina Okafor· Communication score-0.3
In-progress awareness
'In-progress events' counts status transitions, not ticket count. A person who revisits three tickets today is visible as engaged flow — not as scattered work.
People · today
5 of 12 shown| Person | Active | Msg | Cmt | Trend | Score |
|---|---|---|---|---|---|
AC Ani Chen Staff engineer | 6h 52m | 28 | 7 | 8.1 | |
JP Juno Park Senior engineer | 6h 08m | 19 | 3 | 7.4 | |
MF Milo Fischer Engineer | 4h 45m | 12 | 2 | 6.8 | |
RO Rina Okafor Team lead | 6h 35m | 34 | 2 | 7.9 | |
TA Triage Agent AI agent · triage | 12h 00m | 0 | 0 | 8.5 |
FAQ
Jira questions, answered.
If it isn't here, the answer is almost always "no, we don't look at that."
Do you support Jira Server / Data Center?
Not yet — Jira Cloud only. The OAuth 2.0 (3LO) flow and webhooks are Cloud-specific.
Does this handle custom workflows?
Yes. We map Jira status categories (to-do, in-progress, done) so custom workflow names roll up correctly.
Are you compliant with Atlassian's Personal Data Reporting?
Yes. We ship a cron that reports linked account IDs to Atlassian's Personal Data Reporting API. Deletion propagates.
Can I exclude specific projects?
Project-level scoping is on the roadmap. Today, the Atlassian OAuth scopes apply to all projects in the connected site.