Integrations

Connect Jira or Azure DevOps

Frankee reads your real sprint data and writes back only what you explicitly push. Connecting a work tracker is the single setup step that unlocks the most of the product, and it is done once for your whole organization.

Before you start

One work tracker per organization. Connecting Jira while Azure DevOps is connected is refused, and connecting Azure DevOps while Jira is connected is refused. The rule applies in both directions. To move from one to the other, disconnect the first, then connect the second.
Connect at the organization level, configure per team. The authorization happens once. Each Frankee team then points at its own project and board, so several teams can share one connection without sharing a backlog.
An organization admin should do this. They are the person who can also grant the tracker-side permissions the connection needs.

What Frankee writes. Frankee creates work items only when you ask it to: pushing a generated story set, or pushing a triaged action item. It never edits or deletes work that already exists in your tracker, and it never pushes on a schedule or in the background.

Jira

Frankee connects to Jira Cloud using Atlassian's OAuth 2.0 flow. Jira Server and Data Center are not supported.

Connect your organization

Open Org Settings
In Frankee, go to Settings › Org Settings and find the Jira Integration card. If Azure DevOps is already connected, the card is disabled and tells you which tracker is blocking it.
Authorize with Atlassian
Starting the connection sends you to Atlassian's consent screen, where you sign in and approve the access Frankee is asking for. You are approving on behalf of an Atlassian site, so you need permission to grant app access to that site.
Land back in Frankee
Atlassian returns you to the app and the Jira card shows as connected. Nothing further is needed at the organization level.

If your Atlassian account can reach more than one site. Frankee does not currently ask which Atlassian site to use: it connects to the first site your authorization grants access to. If you administer several Atlassian sites and Frankee ends up pointed at the wrong one, disconnect and reconnect from an account whose access is limited to the site you want, and get in touch so we can help you confirm it.

What Frankee can access

The Jira authorization covers:

Reading projects, boards, sprints, issues, and issue details
Reading Jira user information, so Frankee can attribute work correctly
Creating and updating issues, which is what a story or action item push does
A refresh token, so the connection keeps working without you reauthorizing every hour

Point a team at its Jira project

Go to Settings › Team Setup and open the Jira Integration section for the team. Two values are entered by hand:

Jira Project Key. The short uppercase key in your project URL, for example the KEY in .../jira/software/projects/KEY/boards/1.
Jira Board ID. The number at the end of your board URL, for example the 1 in .../jira/software/projects/KEY/boards/1.

The board ID matters more than it looks. Frankee resolves sprints through the board, so Sprint Review, Daily Standup Starter, and the Planning Agent will not find your sprints without it, even when the project key is correct.

Azure DevOps

Frankee connects to Azure DevOps Services (the cloud product at dev.azure.com). Azure DevOps Server, the self-hosted product, is not supported.

You need a work or school account. Frankee authenticates through Microsoft Entra ID, because Microsoft stopped accepting new Azure DevOps OAuth app registrations in April 2025 and is retiring that platform during 2026. Entra cannot issue Azure DevOps tokens for personal Microsoft accounts, and that includes an Azure DevOps account you sign in to with GitHub credentials. If your organization signs in to Azure DevOps that way, the Microsoft sign-in step will refuse the account before it ever returns to Frankee. Connect with a work or school identity in your Entra tenant instead.

Connect your organization

Open Org Settings as an organization admin
Go to Settings › Org Settings and find the Azure DevOps card. Only organization admins can change this connection; other members see the current status and a note saying so. If Jira is already connected, the card is disabled and names Jira as the blocker.
Sign in with Microsoft
You are sent to Microsoft to sign in and consent. Frankee requests the Azure DevOps permissions its app registration holds, plus offline access so the connection can refresh itself.
Choose your Azure DevOps organization
After sign-in, Frankee lists the Azure DevOps organizations your account can reach and asks you to pick one. This is the {organization} in https://dev.azure.com/{organization}. Frankee stores your credentials only once this lookup succeeds, so a failure here leaves you fully disconnected and free to retry.

Point a team at its Azure DevOps project

In Settings › Team Setup, the Azure DevOps section asks for three things. Unlike Jira, these are pickers rather than typed values.

Azure DevOps project
The list shows only projects Frankee can service. See the process template note below if a project you expected is missing.
Azure DevOps team
The team within that project. This is an Azure DevOps team, not a Frankee team. It determines which iterations Frankee reads, so Sprint Review and the standup depend on getting it right.
Area path
Frankee suggests the selected team's default area path where it can, and the field stays editable. Area path controls which board your pushed work items land on. It also keeps teams apart: if two Frankee teams point at one Azure DevOps project, the area path is what stops them reading and filing each other's work.

Supported process templates

Frankee supports Azure DevOps projects on the Agile and Scrum process templates.

Agile projects use User Story work items.
Scrum projects use Product Backlog Item work items.
CMMI and Basic are not supported and do not appear in the project picker at all. This is deliberate rather than an oversight.

Inherited processes count as whichever system process they were derived from, so a customized Agile process still appears, under its own name.

A project missing from the picker is not always a template problem. Frankee tells the two cases apart. Projects it confirmed are on an unsupported template are reported as filtered out. Projects it could not check, usually because your account cannot read them, are reported separately in an amber note with its own retry. If you see that note, the project may well be on a supported template and simply need permissions.

Switching or disconnecting

Switching trackers means disconnecting the current one first. Neither connection will start while the other is live.
Disconnecting Azure DevOps also clears every team's project, team, and area path settings in one step. Reconnecting does not restore them, so each team is reconfigured afterwards. Plan for that before disconnecting a multi-team organization.
Work already pushed stays where it is. Disconnecting removes Frankee's access, not your stories or work items.

Troubleshooting

"Jira is already connected" or "Azure DevOps is already connected"

Expected: one work tracker per organization. Disconnect the named tracker first.

Your connection expired

Both connections refresh themselves. If a refresh fails, usually because access was revoked on the tracker side or a password or policy changed, Frankee asks you to reconnect rather than failing quietly. Reconnecting is the same flow as the first time and does not affect your teams' saved settings on the Jira path.

Sprint Review or Standup says there is no sprint

On Jira, check the team's board ID: sprints resolve through the board, not the project key. On Azure DevOps, check the Azure DevOps team, since iterations belong to a team rather than a project.

Pushed work landed on the wrong board

On Azure DevOps this is almost always the area path. Correct it in Team Setup; already-pushed items need moving in Azure DevOps, since Frankee does not edit work it has already created.

Azure DevOps sign-in refuses your account

See the work-or-school account note above. A personal Microsoft account, including one linked to GitHub credentials, cannot be used for this connection.

How your credentials are stored

Tracker tokens are encrypted at rest against your organization's record. They are internal to Frankee: no API response or settings page ever returns them, and only the account name and the date you connected are shown back to you. Disconnecting clears them.

Still stuck? Signed-in users can reach us from Settings › Contact Support, or use the contact form. Telling us which tracker and which step failed gets you a faster answer.