Does it work with Jira Server or Data Center?

No. It connects to Jira Cloud sites, the ones at yoursite.atlassian.net.

Which Jira projects are read?

Whatever the account you connect can browse. Creating a separate Atlassian account with access to only those projects is how you limit it, and the setup steps suggest exactly that.

Jira integration for Founder OS: what it reads and how to connect

Home Integrations Jira integration

Jira integration

The Jira connector reads the issues updated in the last 90 days from the Jira Cloud site you connect. Founder OS uses them the way it uses Linear issues: to say how much high priority work is open and how much was closed this week.

Connected tools are part of Founder OS, which is on Pro Plus. Idea validation is on every plan, including Free. See every tool Founder OS reads.

What Founder OS reads from Jira

Issues: key, summary and labels
Status category (to do, in progress or done) and priority
Assignee name and resolution date

What it leaves alone:

Issue descriptions, comments and attachments
Boards, sprints and work logs

How much each sync reads

Issues updated in the last 90 days, the 100 most recently updated. A busier site shows as Partly synced

A sync runs when you connect, once a day after that, and whenever you press Sync.

Where the records are used

Ask and the decision log: open issues marked urgent or high priority, and issues closed in the last 7 days

How to connect Jira

Connect with a key you create:

Create a separate Atlassian account for StartupDeckAI that can only browse the projects you want read.
Sign in as that account, open Security, then API tokens, and create a token.
Enter your site name (acme in acme.atlassian.net), that account's email, and the token.

Jira documents this kind of key in its own guide, and you connect your account under Jira’s terms.

Access and security

Your site name (acme in acme.atlassian.net), an account email and an API token for that account. Atlassian cannot limit a token to read access, so the safeguard is ours: every request is checked on our server and anything that is not a read is refused before it leaves.

Every request to a connected tool is checked on our server, and anything that is not a read is refused before it leaves. It cannot move money, send a message or change a record. Keys and tokens are encrypted with AES 256 in GCM mode before they are stored, are never shown again, and are kept out of our logs. Disconnecting deletes the key and every record imported from the tool, in one step. For a tool you approved, we also ask the tool to end our access. The security page sets out the rest.

Questions

Does it work with Jira Server or Data Center?: No. It connects to Jira Cloud sites, the ones at yoursite.atlassian.net.
Which Jira projects are read?: Whatever the account you connect can browse. Creating a separate Atlassian account with access to only those projects is how you limit it, and the setup steps suggest exactly that.

An example of Founder OS reading four connected tools, Stripe, Razorpay, HubSpot and Slack, once a day, then working out monthly recurring revenue, churn and the customer count from the billing records by fixed formulas, each figure labelled Calculated.

Tools & workflows

All integrations Vercel integration Sentry integration Intercom integration Zendesk integration How connected tools are protected

Industry validators

marketplace validator proptech validator agtech validator fintech validator

Comparisons

All tool comparisons Compare vs gbrain Compare vs colrows Compare vs deskferry Compare vs preuve ai

Guides

unit economics explained lean startup methodology 2026 best startup ideas 2026 top startup validation tools 2026

Trust & docs

Research methodology About the team Product changelog Plans and trial limits

Connect Jira to Founder OS

Founder OS reads the tools your company runs on and keeps your figures, notes and decisions in one place. It is part of Pro Plus.

See Founder OS