Integrating Azure DevOps with Jira enhances visibility and traceability between code changes and project management. Here's how you can include issue keys in these changes.
When you include issue keys in branch names, commit messages, and pull requests, you'll see development information on the Jira work item's development panel.
Find the issue key
In Jira, the issue key is a unique identifier associated with each individual work item. It is typically a short code, often consisting of uppercase letters followed by a hyphen and a number (e.g., TEST-2). Here are several ways to find the Jira issue key:
-
If your Jira instance uses Agile boards (Scrum or Kanban boards), the issue key is usually visible on the board, at the bottom left of each work item card:
Work item cards also display development icons (on the right bottom corner) to indicate when they have pull requests, branches, or commits associated with them.
-
When you open a Jira work item, the issue key is usually displayed prominently in the breadcrumb navigation at the top of the work item page:
-
The Jira issue key is a part of the work item's URL. When you navigate to a work item, check the URL in your browser's address bar for the issue key. It is typically located after the last slash.
Reference Jira work items in development activities
Once you've found the issue key, reference it in your branch names, commit messages, and pull requests to link that activity back to the Jira work item. For examples and the full set of options, see Get started for Jira end-users.
Updated: August, 2026