This guide explains how to create a branch in Azure DevOps Server (On-Premises) directly from a Jira work item, without leaving Jira, using Azure DevOps for Jira.
This guide covers Azure DevOps Server (On-Premises). For Azure DevOps Cloud, see "Creating Azure DevOps (Cloud) Branches from Jira" instead.
Before you begin
Make sure you have:
-
Access to view the Jira work item you want to branch from.
-
The Create branch permission on the Azure DevOps repository you'll be branching in. This is an Azure DevOps permission, not a Jira one, so it's controlled by your Azure DevOps access level and repository permissions rather than anything in Jira.
-
A Personal Access Token with Code (Write) scope.
-
An Azure DevOps Server that's reachable from the internet, so Azure DevOps for Jira can connect to it.
Creating a branch this way uses your own Azure DevOps identity. Nobody else's access is affected, and no separate admin setup is needed beyond your admin having connected the relevant Azure DevOps project to Jira.
Step 1. Open Create branch on a Jira work item
-
Open the Jira work item you want to branch from.
-
Expand the Azure DevOps section on the work item.
-
Select Create branch.
The info banner explains why the branch name matters: Create branch automatically includes the work item's key in the branch name, which is what links the branch, and anything committed to it, back to this work item.
If your admin hasn't connected the relevant Azure DevOps project to Jira yet, you'll see a message about it here instead of the Create branch button. Only a Jira admin can complete that step.
You might also notice a small + icon next to "branches" in the work item's standard Developmentpanel, with a "Create new branch" tooltip. This is a generic Jira feature unrelated to branch creation in Azure DevOps for Jira.
Step 2. Connect with a Personal Access Token
The first time you create a branch, you'll be asked to connect with a Personal Access Token. You only need to do this once. The token needs Code (Write) access.
Enter your PAT and your Azure DevOps Server URL. Leave Is Cloud PAT? off.
Once it validates, an Azure DevOps Organization name field appears, and a green Connection is successful! message confirms you're good to go before Connect and continue becomes selectable.
Step 3. Fill in the branch details and create
This all happens on one screen, titled Create Branch for [work item key]:
-
Select the Organization.
-
Select the Project.
-
Select the repository.
-
Select the parent branch to create from.
-
Check the Branch name field. It's filled in automatically from the work item's key and summary, with spaces in the summary replaced by hyphens - for example, a work item
TP-30titled "ADO Server Branch Creation" pre-fills asTP-30-ado-server-branch-creation. Edit it if you'd prefer something different. -
Select Create.
If the project you pick isn't connected to Jira yet, you'll see a prompt about it here instead of being able to continue. Ask a Jira admin to connect it first.
Once created, you'll see a confirmation with a link to view the new branch directly in Azure DevOps.
The new branch also appears right away in the work item's standard Development panel, alongside its commits, pull requests, builds, and deployments.
Managing your connection
Select Manage connection at the bottom of the Create Branch screen to update or delete your Personal Access Token. Deleting it loses the current connection.
If you see "No access to Azure DevOps"
If your connection breaks - for example, an expired token, a token missing the required scope, or the server becoming unreachable from the internet - the Create Branch screen shows this instead of letting you continue. The organisation, project, and branch fields stay visible but greyed out with loading errors, and Create is disabled.
Select Manage connection to reconnect. For other causes of this same error, see How to fix "No access to Azure DevOps" error when creating a branch?.
Related guides
Updated: August, 2026