Leanmote

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.

Sprints with start, end, and committed-scope snapshots.

Custom fields used in metrics (Story Points, Original Estimate).

- 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).

Open <code>Administration → Productivity Tools</code>.

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 (listed below).

Select the projects to track. Less is more — start with active projects only.

1. Open <code>Administration → Productivity Tools</code>.
2. Find Jira under Project Management and click Connect.
3. Sign in with an Atlassian account that has access to the Jira site you want to integrate.
4. Authorize the requested scopes (listed below).
5. Select the projects to track. Less is more — start with active projects only.
6. Click Save.

<code>read:jira-work</code> — read issues, sprints, and status history. This is the data that drives every metric.

<code>read:jira-user</code> — read user accounts so we can map Jira identities to Leanmote teammates.

<code>read:me</code> — read the connecting account's profile.

<code>offline_access</code> — refresh the access token in the background so the integration keeps syncing without re-authentication.

<code>write:jira-work</code> — required so Leanmote can post comments and apply transitions on your behalf when you opt into agentic features (for example, the Leanmote Bot answering documentation tickets in your project). Reporting and analytics never use this scope.

- <code>read:jira-work</code> — read issues, sprints, and status history. This is the data that drives every metric.
- <code>read:jira-user</code> — read user accounts so we can map Jira identities to Leanmote teammates.
- <code>read:me</code> — read the connecting account's profile.
- <code>offline_access</code> — refresh the access token in the background so the integration keeps syncing without re-authentication.
- <code>write:jira-work</code> — required so Leanmote can post comments and apply transitions on your behalf when you opt into agentic features (for example, the Leanmote Bot answering documentation tickets in your project). Reporting and analytics never use this scope.

If your security team prefers to disable the agentic features, contact your account team — we can deploy a connection variant that omits <code>write:jira-work</code>, at the cost of those features.

For accurate cycle time, WIP, and rework metrics, Leanmote needs each Jira status mapped to one of four kinds: backlog, active/in-progress, waiting/review, or done.

Jira statuses are not auto-mapped on first sync. Until you configure a mapping, statuses are unmapped and Jira tasks may be missing from WIP, cycle-time, and backlog charts. Two ways to set the mapping:

AI-assisted — Leanmote can suggest a mapping based on each status's name. Open the Jira card in <code>Administration → Productivity Tools</code> and click the auto-map action; review and accept the suggestions.

Manual — assign each status to a kind directly from the same screen.

- AI-assisted — Leanmote can suggest a mapping based on each status's name. Open the Jira card in <code>Administration → Productivity Tools</code> and click the auto-map action; review and accept the suggestions.
- Manual — assign each status to a kind directly from the same screen.

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.

Cycle time looks wrong — usually a status-mapping issue. Re-check active vs. waiting state assignment.

Tasks missing from charts — most charts skip tasks with unmapped statuses. Run the AI auto-mapper or finish manual mapping.

Permission errors — the connecting user must have project-level read access. Service-account installs avoid this.

- Cycle time looks wrong — usually a status-mapping issue. Re-check active vs. waiting state assignment.
- Tasks missing from charts — most charts skip tasks with unmapped statuses. Run the AI auto-mapper or finish manual mapping.
- Permission errors — the connecting user must have project-level read access. Service-account installs avoid this.

- Integrations overview
- Connect your first integrations
- Why a metric looks off

Connect Jira so issues, sprints, and status history populate flow metrics.

Jira integration

Sign In

Roadmap & Feedback

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

Try using different keywords or checking for typos.

No conversations found

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Home

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Track the progress of all tickets and conversations related to your company.

Customer Portal.

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

Search and ask

Find guides, answers, and references.

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.

Jira integration

What Leanmote pulls from Jira

Connect Jira

OAuth scopes requested

Status mapping

Sprints

Common issues

Related articles