Jira Server integration for PI Planning
Still on Jira Server? Kendis connects to it with OAuth or a username and password, and syncs epics, features, stories, sprints and dependencies both ways while you plan your move to Jira Cloud or Data Center.
- Two-way sync
- OAuth or password
- Cloud or self-hosted
Kendis and Jira Server at a glance
- Connect with
- OAuth 2.0 or OAuth 1.0a through Application Links, or a username and password
- Sync
- Two-way. Kendis writes through the Jira REST API and a Jira webhook sends changes back
- Hosting
- Kendis Cloud if Jira Server is reachable from the internet; self-hosted Kendis if it is only reachable inside your network
- Moving off Server
- The same Kendis boards connect to Jira Cloud or Data Center when you migrate
Atlassian ended support for Jira Server on 15 February 2024. Kendis still connects to it, and the same boards connect to Jira Cloud or Jira Data Center when you migrate.
How to connect Jira Server to Kendis
About fifteen minutes for an admin.
Choose how to connect
Use OAuth 2.0 through Application Links for the most secure setup, or a username and password.
Set up OAuth in Jira
A Jira administrator creates an incoming External application link with the Kendis redirect URL and Admin permission.
Authorise Kendis
Paste the client ID and secret into the Kendis ALM account and request the auth token.
Connect each user
Each planner authorises their own OAuth token from their Kendis profile.
Build the board
Fetch features with a Jira filter or JQL, map team sprints and start planning.
What syncs between Kendis and Jira Server
Synced both ways
- Epics, Features or any parent issue type, chosen with a Jira filter or JQL
- Stories linked by Epic Link, Parent Link or any Jira link type
- Sprints, mapped per team to a Jira project and board
- Dependencies as Jira issue links
- Summary, key, status, sprint and story points, plus up to 5 extra fields for features and stories
- Start and end dates for features and stories
Good to know
- Atlassian ended support for Jira Server on 15 February 2024, so plan your move to Jira Cloud or Data Center
- With OAuth there is no password option for users
- A captcha on the Jira login page can block password connections
- If Jira sits behind a VPN, run Kendis self-hosted so it can reach Jira directly
Step-by-step setup guides
Setup guides in the Kendis help center
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 Jira Server.
Yes. Kendis connects to Jira Server with OAuth 2.0, OAuth 1.0a or a username and password, and syncs both ways.
Plan a move to Jira Cloud or Jira Data Center. Kendis connects to both, so your boards and planning process carry over. Note that Data Center itself ends on 28 March 2029; see the Data Center end-of-life guide.
Yes, with self-hosted Kendis. Kendis Cloud cannot reach a Jira that sits behind a VPN, so run Kendis on Docker, OpenShift or Linux inside your network.
OAuth 2.0 or OAuth 1.0a through Jira Application Links, both set up by a Jira administrator, or a username and password.
Yes. Dependencies between Jira items sync both ways as Jira issue links.