Skip to main content
Connect Jira to sync your issues, epics, and project data for task-based metrics.

​
What’s synced

  • Issues and their status
  • Epics and story points
  • Sprint data (sprint names, dates, and status — requires the Agile Boards OAuth scopes below)
  • Project structure
  • Assignees and reporters

​
Connecting Jira

Weave connects via Atlassian OAuth 2.0 with these scopes:
  • read:jira-user — read Jira user profiles
  • read:jira-work — read issues, projects, and boards
  • manage:jira-webhook — manage webhooks for real-time updates
  • read:board-scope:jira-software — read Agile board metadata (needed for sprint sync)
  • read:project:jira — read Jira project metadata (needed for sprint sync)
  • read:sprint:jira-software — read sprint metadata (needed for sprint names and dates)
1

Start connection

Go to Data and click Connect on Jira
2

Authorize Weave

Sign in to Jira and authorize the Weave app
3

Select projects

Choose which projects to sync
If you connected Jira before sprint sync scopes were added, reconnect in Data → Jira so Weave can issue a token with the Agile Boards permissions. Task-level sprint membership still syncs from issue fields without these scopes, but sprint names and dates require them.

​
Metrics enabled

Once connected, you can track:
  • Task delivery — How many tasks are completed over time
  • Task lead time — Time from creation to completion
  • Points delivered — Story points completed
  • Bug tasks — Bug-related issues

​
Linking tasks to PRs

Weave automatically links PRs to Jira issues when:
  • The PR title or branch name contains the issue key (e.g., PROJ-123)
  • The PR description mentions the issue key
This enables end-to-end tracking from task creation to code delivery. These links also determine how PRs are categorized in R&D capitalization project breakdowns.
Last modified on October 15, 2026