How to Create an Azure DevOps Branch from Jira

Creating a branch directly from a Jira issue keeps your commit history tied to the work it belongs to. No copying issue keys, no switching tabs to Azure DevOps, no mistyped branch names. With Azure DevOps for Jira, you can create an Azure DevOps branch from inside Jira in under 30 seconds — and every commit on that branch automatically links back to the issue.

This guide walks through the full setup and step-by-step process, including permissions, OAuth configuration, and workflow best practices that make this worth doing right.

Why Create Branches from Jira?

Most teams already reference Jira issue keys in their branch names. The problem is that this convention depends entirely on humans remembering to do it — and doing it consistently. Creating branches directly from Jira solves three things at once:

• Automatic naming consistency. Every branch gets the issue key baked into its name. No more fix-login-bug branches that nobody can trace back to a ticket.
• Bi-directional traceability. Jira's development panel shows the branch, its commits, and any pull requests. Your Azure DevOps repo links back to the Jira issue. Auditors and project managers get visibility without asking developers.
• Workflow automation triggers. Once branches and PRs are linked to Jira issues, you can build automation rules that transition issues when a PR is merged or a branch is created. More on that in our guide to integrating Jira with Azure DevOps.

Prerequisites

Before you create your first branch, make sure these three things are in place.

1. Enable Third-Party Application Access via OAuth

Azure DevOps organizations block third-party OAuth access by default. An organization admin needs to enable this, or branch creation will fail silently. To enable it, open your Azure DevOps Organization settings, go to Policies under the Security section, and switch Third-party application access via OAuth to On.

This is an organization-level setting, not a project-level one. If you work across multiple Azure DevOps organizations, each one needs this enabled separately.

2. Verify Create Branch Permissions

The user creating the branch needs the Create branch permission in the target Azure DevOps repository. This is typically granted through the Contributors group, but custom permission schemes may restrict it. To confirm, go to Project Settings > Repositories, select the repository, open its Security tab, and check that the user or their group has Create branch set to Allow.

3. Install Azure DevOps for Jira

You need the Azure DevOps for Jira app installed on your Jira instance. The app connects your Jira Cloud site to your Azure DevOps organizations and enables the branch creation workflow in Jira's development panel. Installation takes a couple of minutes from the Atlassian Marketplace.

Step-by-Step: Create an Azure DevOps Branch from Jira

Once your prerequisites are set, here is the process for creating a branch.

Step 1: Open the Jira Issue

Navigate to the Jira issue you want to create a branch for. On the right side of the issue view — or at the bottom on smaller screens — you will find the Development panel. This panel is where linked branches, commits, and pull requests appear, and where a Create branch link is shown when no branches exist yet.

Step 2: Click Create Branch

You have two ways to reach the branch creation dialog:

• Option A: Click the Create branch link directly in the development panel.
• Option B: If branches already exist for this issue, hover over the branch count, click the + icon, then select Create branch in Azure DevOps.

Step 3: Authenticate with Microsoft

The first time you create a branch — or after your session expires — you will be prompted to sign in through the standard Microsoft OAuth flow. Use the account that has access to your Azure DevOps organization. After authentication, the app remembers your session, so you will not need to sign in every time.

Step 4: Configure the Branch

The branch creation dialog presents several fields:

• Organization: Select the Azure DevOps organization where the repo lives.
• Project: Choose the project within that organization.
• Repository: Select the target repository.
• Parent branch: Pick the branch to create from (usually main or develop).
• Branch name: This auto-populates with the Jira issue key and summary. You can edit it, but keeping the issue key in the name is recommended.

Step 5: Click Create

Click the Create button. The branch is created in Azure DevOps immediately and appears in the Jira issue's development panel within seconds. Any commits pushed to this branch will now show up in Jira automatically.

Branch Naming Best Practices

The auto-generated branch name uses the pattern ISSUE-KEY-issue-summary. This works well out of the box, but consider these adjustments for your team:

• Keep it short. Long issue summaries create unwieldy branch names. Trim the auto-generated name to something meaningful but concise — PROJ-123-login-fix beats PROJ-123-fix-the-login-page-when-users-click-submit-button-twice.
• Use prefixes for branch types. If your team follows a branching strategy like GitFlow, prepend the type: feature/PROJ-123-login-fix or bugfix/PROJ-456-null-check.
• Always keep the issue key. Whatever naming convention you use, the Jira issue key should stay in the branch name. This is what links commits and PRs back to the issue.

CI/CD Implications

Branches created from Jira work exactly like any other Git branch in Azure DevOps — your existing CI/CD pipelines pick them up automatically. But the Jira linkage opens up some additional possibilities:

• Gate deployments on Jira status. Use Jira issue status as part of your deployment approval process. If the linked issue is not in "Ready for Deploy" status, block the pipeline.
• Auto-transition issues on pipeline events. When a build succeeds or a PR merges, automatically move the Jira issue to the next status. See our guide on automating Jira and Azure DevOps workflows for more on this.
• Release notes generation. Because every branch (and therefore every PR) maps to a Jira issue, you can auto-generate release notes from the issues included in a release.

Troubleshooting

If branch creation is not working, check these common issues:

• "Unable to connect to Azure DevOps" — Third-party OAuth access is likely disabled. Have an org admin enable it in Azure DevOps organization settings under Policies.
• "Permission denied" or branch not created — The authenticated user does not have the Create branch permission in the target repository. Check repository security settings in Azure DevOps.
• Organization or project not showing — Make sure you are signed in with the correct Microsoft account. If you belong to multiple Azure DevOps organizations, the account you authenticate with determines what you see.
• Development panel not visible — Ensure the Azure DevOps for Jira app is installed and configured. A Jira admin may also need to enable the development panel in the issue layout.

For detailed configuration instructions, see the official help documentation.

Beyond Branches: Full Development Visibility

Branch creation is just the starting point. Once branches are linked, the Jira development panel also tracks commits, pull requests, and builds. If your team also works with GitHub or GitLab alongside Azure DevOps, Jigit provides the same branch-and-PR tracking across all three platforms from a single Jira integration.

The goal is the same regardless of which tool you use: every piece of development work should trace back to a Jira issue without requiring manual effort from developers. Creating branches from Jira is the simplest first step toward that.