Issues & support
Set up Jira
Connect Jira Cloud to make your issues searchable — each becomes a document with its description and comment thread, tied to its project, assignee and reporter. Read-only.
Before you start
- id.atlassian.com → Security → API tokens → Create API token, signed in as the account whose email you'll enter below.
- Copy it right away — Atlassian shows it once.
- Issues are read as that account — it sees exactly the projects the account can see.
- Documents → Jira, enter Site (your-domain.atlassian.net — pasting the full URL is fine) and Account email.
- Paste the API token.
- Projects: optional project keys, one per line (e.g. OPS) — blank syncs every project the account can see.
- JQL (Advanced): optional, replaces the Projects filter with your own query, e.g. project = OPS AND created >= -365d.
- Choose access groups, Test, then Sync.
What comes in
- Each issue becomes a document: summary, description and the full comment thread, tied to its project, type, priority, assignee, reporter and labels.
- Each project also becomes a findable concept.
Access
Each project's issues follow who holds Browse access there — Jira's own permission scheme, expanded through its groups and roles into people, re-checked as the source syncs. An issue carrying a security level narrows further, to just its assignee and reporter, because Jira doesn't expose that level's own member list to this account. Where an account can't be matched to an email, or a project's permission scheme can't be read (needs project-admin rights), that issue falls back to this source's access groups instead. Switch How access works to “One list for everything” under Permissions to put everything this source brings in under the chosen access groups instead.
Read-only; the v2 API is used so descriptions and comments arrive as plain text. An account that hides its email address can't be matched to a person here and is covered by this source's access groups instead.
Last updated 20 Sep 2026