Jira
Jira adds task-level context: what tickets you worked on, status transitions (“moved to In Review”), and sprint membership.
Connect
Section titled “Connect”devrecall auth jiraTwo auth options (chosen interactively during the prompt):
- Atlassian OAuth (3LO) — opens a browser via
relay.devrecall.dev. Recommended. - API token — generate at id.atlassian.com → Security → API tokens and paste it when prompted.
Both Cloud and Server / Data Center are supported. DevRecall detects which based on your base URL.
What gets collected
Section titled “What gets collected”| Activity | What |
|---|---|
| Issue transitions | When you moved a ticket between statuses |
| Comments | Comments you wrote |
| Issues created | Issues you reported |
| Sprint membership | Which sprint, velocity contribution |
| Worklogs | Time logged (if your team uses worklogs) |
Read-only. DevRecall never creates or modifies issues.
Required scopes
Section titled “Required scopes”| Scope | Purpose |
|---|---|
read:jira-work | Read issues, projects, boards, sprints |
read:jira-user | Read user profiles for identity resolution |
offline_access | Refresh token for background sync |
How standups link Jira → Git
Section titled “How standups link Jira → Git”When a commit message contains a Jira issue key (e.g., PROJ-123: fix retry logic), DevRecall groups commits under their tickets in
generated standups:
- PROJ-123 (Fix payment retry): 3 commits — backoff, max retries, tests- PROJ-123: moved to In ReviewThis is automatic — no extra setup.
Rate limits
Section titled “Rate limits”Atlassian recommends ≤100 requests/minute per user. DevRecall uses JQL to fetch all relevant issues in a single query — a typical daily sync is 5–10 requests.
Confluence
Section titled “Confluence”Confluence pages you’ve edited are not yet collected. Planned for a later release — useful for brag docs (“authored 3 RFCs in Q1”).