Integrations: Jira and Azure DevOps, synced both ways
Kendis plans on top of the tools your teams already use. Features, stories, sprints and dependency links stay in Jira or Azure DevOps, and every change syncs both ways in real time.
- Two-way, real-time sync
- Cloud or self-hosted
- ISO/IEC 27001 certified
Choose your ALM tool
Five supported connections, each with its own setup guide.
Jira Cloud
Connect with an API token or the Kendis app from the Atlassian Marketplace.
Learn moreJira Data Center
Connect your self-managed Jira with OAuth through Application Links.
Learn moreJira Server
Keep planning on Jira Server while you plan your move to Cloud or Data Center.
Learn more
Azure DevOps
Connect Azure DevOps Services with a personal access token or OAuth.
Learn moreMicrosoft TFS
Connect Team Foundation Server 2018 and 2019, now Azure DevOps Server.
Learn moreHow the Jira and Azure DevOps sync works
The same five steps for every integration.
Connect an ALM account
Add your Jira or Azure DevOps URL and an API token, personal access token or OAuth, then test the connection.
Turn on real-time updates
Kendis writes changes through the REST API and listens for changes through a Jira webhook or Azure DevOps service hook.
Choose the work
Bring in features with a Jira filter or JQL, or an Azure DevOps query. Linked stories follow automatically.
Map teams and sprints
Map each team to its Jira board and sprints, or its Azure DevOps team, area path and iterations.
Plan both ways
Edit on the board and the change is written to your ALM tool. Edit in Jira or Azure DevOps and the board updates.
What Kendis syncs with Jira and Azure DevOps
| Jira | Azure DevOps and TFS | |
|---|---|---|
| Choosing the work | A Jira filter or JQL query brings in Epics, Features or any parent issue type | A query or WIQL brings in Features or any parent work item type |
| Stories | Children follow Epic Link, Parent Link or any Jira link type you choose | Linked child work items come in with their parent |
| Teams and sprints | Each team maps to a Jira project, board and sprints | Each team maps to a project, team, area path and iterations |
| Dependencies | Synced as Jira issue links | Synced as link types such as Successor and Predecessor |
| Fields | Summary, key, status, sprint and story points, plus up to 5 extra fields for features and stories | Status, item types, and estimate and due-date fields mapped per project |
| Real-time updates | Jira webhook | Azure DevOps service hook |
Kendis Cloud or self-hosted
Where Kendis runs depends on where your Jira or Azure DevOps runs.
Kendis Cloud
- EU hosting on OVHcloud in Frankfurt, or US hosting on AWS
- Works with Jira Cloud and Azure DevOps Services
- Works with Jira Server or Data Center when your Jira is reachable from the internet
- ISO/IEC 27001 certified, GDPR compliant
Kendis self-hosted
- Runs inside your network on Docker, OpenShift or Linux
- Needed when your ALM tool is only reachable inside your network, for example Jira behind a VPN
- The Docker edition makes no external calls outside your enterprise network
- LDAP sign-in available
Permissions and security
Changes under your own name
- An admin creates the central connection once
- Each user adds their own ALM credentials, so edits in Kendis show under their name in Jira or Azure DevOps
- Jira Cloud users can use scope-based API tokens
Control who can edit
- Board admins can make a board read-only for users without personal ALM credentials
- Works for Jira and Azure DevOps or TFS boards
- Self-hosted Kendis keeps planning data inside your network
Connect your Jira or Azure DevOps and plan free
Kendis is a PI Planning and tracking platform that sits on top of Jira and Azure DevOps. The free trial runs for six months, long enough to plan and track two full PIs with your real backlog before anyone has to approve a budget.
One trial per organisation that has not used Kendis in the last twelve months. After the trial, Premium Cloud is $14 per user per month billed annually, or $16 monthly, and you license only the people who plan. See pricing and the free trial terms.
- 6 months free, no credit card
- Choose EU hosting (OVHcloud, Frankfurt) or US hosting (AWS)
- Two-way sync with Jira Cloud, Jira Data Center and Azure DevOps
- Planning board, dependencies, PI objectives, ROAM risks, solution boards
- ISO/IEC 27001 certified, GDPR compliant, DORA Schedule available
- No user caps and no setup costs during the trial
Frequently asked questions
What teams ask before they connect Kendis.
Kendis integrates with Jira Cloud, Jira Data Center, Jira Server, Azure DevOps Services and Microsoft Team Foundation Server (TFS) 2018 and 2019. Each connection is two-way and real-time.
Yes. Changes made in Kendis are written to Jira or Azure DevOps through the REST API, and changes made in Jira or Azure DevOps reach Kendis through a webhook or service hook, so the board and the backlog stay in step.
To create the Jira webhook automatically, the connecting user needs System Admin or Super Admin rights in Jira; otherwise an admin can create it manually. OAuth setups for Jira Server, Jira Data Center and Azure DevOps also need an administrator.
No. If your Jira or other ALM tool is only reachable inside your network, run Kendis self-hosted on Docker, OpenShift or Linux so it can reach your ALM tool directly.
Yes, once you add your own ALM credentials to your Kendis profile. Without them, changes appear under the user configured in the central ALM connection.
Every integration has step-by-step guides in the Kendis help center, linked from each integration page.