Integrations
Connect Kansov to Jira (two-way sync + push), Google Calendar, Microsoft Outlook, ICS feeds, the Browser Extension, and AI assistants like Claude. Step-by-step setup for each.
Color key: Blue steps happen inside Kansov. Green steps happen inside the external application or service.
Jira Cloud Integration
Kansov connects bi-directionally to Jira Cloud. Sync tickets from Jira into Kansov as Insights (customer signal flows in), and push Kansov Features to Jira as Epics (engineering handoff flows out). Both directions are optional and configured independently.
Jira Cloud only. Server and Data Center are not supported. Admin access to both Jira and Kansov is required to set up the integration.
Step 1 — Create the OAuth app in Atlassian
Done once per workspace. These steps happen in Atlassian's Developer Console, outside Kansov.
Go to developer.atlassian.com → My Apps → Create → OAuth 2.0 integration. Give it a name (e.g. "Kansov"). Note the Client ID and Client Secret — you'll paste both into Kansov in Step 2.
Under Authorization, set the Callback URL to: https://[your-kansov-domain]/api/integrations/jira/callback
Under Permissions → Jira platform REST API → Configure:
read:jira-work&read:jira-user— required to sync Jira issues into Kansovoffline_access— required so tokens can refresh; without it, the integration breaks every hourwrite:jira-work— only required if you want to push Kansov Features to Jira as Epics. Skip if you only need inbound sync.
If you add write:jira-work later to an already-connected workspace, you'll need to disconnect Jira in Kansov and reconnect — Atlassian only grants newly added scopes on a fresh authorization.
Step 2 — Connect in Kansov
Go to Settings → Integrations & MCP → Integrations, find the Jira card, click Configure credentials. Paste the Client ID and Client Secret from Atlassian, then Save.
Kansov redirects you to Atlassian to authorize the app. Approve it; you'll be bounced back to Kansov with the integration marked as Active.
Step 3 — Configure sync (Jira → Kansov Insights)
In the Jira integration card, click Configure. For each Jira project you want to sync, pick:
- Issue types — which ticket types to pull (Bug, Story, Feature Request, Emailed request, etc.). Different projects can have different selections.
- Labels (optional) — when set, tickets matching any selected issue type or any label from this project are synced. Useful for pulling only specifically-tagged work from a dev project.
Also in the same sheet, configure Field mappings:
- Company — maps a Jira field to Kansov's Customer. For Service Desk projects, Organizations works; for software projects, Components or Project Name.
- Customer Email — set to Reporter to pull the ticket reporter's email onto the Kansov Insight.
- Auto-create company — when on, a new Kansov customer is created if the mapped company name isn't already present.
Save. Kansov will sync hourly, or click Sync Now for an immediate run. Each Jira ticket that matches your filter becomes a Kansov Insight with an Origin card linking back to the source ticket.
Step 4 — (Optional) Enable push: Kansov Feature → Jira Epic
If you want your PMs to hand off Kansov Features to engineering as Jira Epics in one click, enable push in the same Configure sheet:
In Settings → Integrations & MCP → Integrations → Configure (Jira), scroll to the Push features to Jira section. Toggle it on.
All Epics created from Kansov Features land in this one project. You can change it later; existing pushed Features keep their original Epic link.
Comma-separated. These labels are added to every Epic created from Kansov, in addition to the always-applied from-kansov marker. Handy for sprint planning filters (e.g. product-backlog, q1-roadmap). Don't re-type from-kansov — it's added automatically.
After saving, any user with write access on Features (Admin, PM, or Contributor roles) will see a Create Jira Epic button on the Feature detail view. Viewers cannot push.
What happens when a user clicks "Create Jira Epic"
- A new Epic is created in your configured Jira project with the Feature's title and description.
- The Epic is labeled
from-kansov(plus any defaults you configured) so you can find all Kansov-originated Epics with a JQL query:labels = "from-kansov". - The Epic's Reporter is set to the Kansov user who clicked, if their email matches an Atlassian account on your tenant. If no match, Reporter falls back to the user who connected Kansov to Jira.
- Jira's Web Links section on the Epic carries a clickable link back to the Kansov Feature — so engineers can navigate between the two.
- In Kansov, the "Create Jira Epic" button is replaced with an Origin card showing the Jira Epic key, live status, priority, and an "Open in Jira" button.
How Jira status stays in sync on the Kansov side
Kansov automatically refreshes the Epic's status and priority from Jira once an hour, and also on any manual Sync Now. The refresh only updates display-only fields on the Origin card — it does not change the Kansov Feature's own status. PMs stay in control of the Feature record; engineers stay in control of the Epic.
Tip — auditability. Because every pushed Epic is labeled from-kansov, your engineering leads can pull a monthly report of "everything requested via Kansov" with a one-line JQL filter. Combined with the Web Link back to Kansov, this gives clean bidirectional traceability from customer signal to engineering delivery.
MCP Server (Claude Desktop & Cursor)
Kansov exposes an MCP (Model Context Protocol) server that lets AI assistants like Claude Desktop and Cursor read and write your Kansov data using natural language commands.
Go to Settings → Integrations & MCP → MCP Clients. Click Generate Token. Copy the token and note your MCP server URL.
Open Claude Desktop settings → Developer → Edit Config and add a server entry with your Kansov MCP URL and token.
Restart Claude Desktop. Try: "List my 5 most recent Insights in Kansov".