The Jira integration is the most common planning-side data source for Leanmote. It powers throughput, cycle time, WIP, and waiting-time metrics, and contributes to Sprint Efficiency.
What Leanmote pulls from Jira
Projects you select.
Issues with full status-change history.
Sprints with start, end, and committed-scope snapshots.
Custom fields used in metrics (Story Points, Original Estimate).
Connect Jira
Open
Administration → Productivity Tools.Find Jira under Project Management and click Connect.
Sign in with an Atlassian account that has access to the Jira site you want to integrate.
Authorize the requested scopes.
Select the projects to track. Less is more — start with active projects only.
Click Save.
Permissions
Leanmote requests only read-only scopes — no write access to Jira. The integration needs read access to issue, sprint, and status-history data, plus user-profile access to map Jira identities to Leanmote teammates.
Status mapping
For accurate cycle time and WIP, Leanmote needs to know which Jira statuses are active (in progress, in review, QA) and which are waiting (blocked, awaiting external dependency). After connecting, open the Jira integration's card in Administration → Productivity Tools and verify the auto-detected status mappings.
Sprints
If your Jira boards use sprints, Sprint Efficiency starts populating once two complete sprints have closed. Boards without sprints simply won't show that metric.
Common issues
Cycle time looks wrong — usually a status-mapping issue. Re-check active vs. waiting state assignment.
Story Points missing — confirm the Story Points field is enabled on the project's issue types.
Permission errors — the connecting user must have project-level read access. Service-account installs avoid this.
Related articles
Integrations overview
Connect your first integrations
Why a metric looks off