VSTS/Azure DevOps Integration Jira Cloud
Connecting to VSTS/Azure DevOps Jira Cloud
The Git Integration for Jira app supports Azure DevOps.
This process requires an existing Microsoft account with VSTS or Azure DevOps git projects.
- On your Jira Cloud dashboard menu, go to Git > Manage Git Repositories.
- The git configuration page for connecting repositories is displayed.
- On the Auto-connect integration panel, click Microsoft.
- On the following screen, select Visual Studio Team Services (VSTS). If you
are using Azure DevOps, select it from the list instead. Click
- Login to your Microsoft account, if prompted.
- The following permissions screen is displayed:
- Click Accept
to authorize access for Git for Jira Cloud.
- Repositories of the logged in Microsoft user can be automatically connected to
Jira Cloud. Repositories that are added or removed from VSTS/Azure DevOps will be
likewise connected or disconnected from Jira Cloud.
- Click Connect. For now, only git
projects are supported from VSTS/Azure DevOps.
Setting Up VSTS/Azure DevOps Web Links
The Git Integration for Jira app automatically configures web
linking for VSTS/Azure DevOps git repositories.
Working with Branches and Pull Requests with VSTS/Azure DevOps Jira Cloud
This process requires a VSTS or Azure DevOps git repository AND a PAT with at least
Code (read and write) scope.
- On your Jira Cloud, open a Jira issue. On the Jira developer panel
under Git Commits, click Create Branch.
- The following dialog is displayed:
Click Create Branch. The newly-created
branch is now listed in the developer panel under Branches.
On your VS IDE, go to Team Explorer and perform a Pull action. This
will update your local repository with a new branch list.
Go to Team Explorer > Branches.
Under Active Repositories, expand the remote/origin folder view.
Right click the new branch then select Checkout. The new branch will
be listed in the active repositories list.
Make changes to a file to prepare it for commit and branch merge.
On the Team Explorer, click Changes.
- Select a Repository from the list.
- Choose a Base branch.
- Enter a Branch name or leave it as is (recommended).
- Make sure that Branch: displays the name of the
newly-created branch. If not, select it again from the list.
- Add the Jira issue key to the commit message. (Underlined in red).
This will associate the commit to the mentioned Jira issue key.
- Click the dropdown on the Commit All
button then select Commit All and Push.
The commit is pushed to the new branch and is now ready for merge.
VSTS/Azure DevOps Pull Request
The pull request feature works the same as merge request.
To create a pull request and merge it to the main source (master):
- On your Jira Cloud, open the Jira issue where your previously created a branch.
- On the developer panel under Git Commits,
click Create Pull Request.
- The following dialog is displayed:
Click Create to create the pull request.
- Select Repository from the list.
- Choose the newly-created branch as the Source branch.
- Set master as the Target branch.
- Enter a descriptive title or leave it as is (recommended).
The pull request is listed on the developer panel of the Jira issue page.
The pull request is also ready for approval by the reviewers in your VSTS or Azure DevOps
VSTS/Azure DevOps Merging Branch to master
Continuing from the above steps, the current branch is ready for merge.
- On the Team Explorer, update your local repository by performing a
- Go to Pull Requests.
The pending pull request items are displayed here. Pull requests
requires the approval of the reviewers before it can be merged from the VS IDE.
- Go to Branches. Click
- The following screen is displayed:
Click Merge to continue.
- Set the source to the branch to which you pushed the commits.
- Set the target branch to master.
The reviewer's approval is required to completely merge the pull request. This
usually takes place in the VSTS or Azure DevOps portal where your updated code is being reviewed.
Once approved, the team leader or reviewer can then complete the merge. The
commit can be viewed in the associated Jira issue page.