Git links are now available on the developer panel in the following screens:
Therefers to an existing Git Commits view, which the issue tab have now. Clicking this text link will reload the page and automatically selects the Git Commits tab to view the commits.
Therefers to an existing Git Roll Up view, which the issue tab have now. Clicking this link will reload the page and automatically selects the Git Roll Up tab to view the git code summary.
Jira Server Only Click to compare code diff of different branches. It will open the following dialog:
Select a Repository. Set Compare branch and Base branch then click Compare to proceed. The view redirects to the Repository browser Compare page showing changes between the compared branches.
The Branches section lists the branches names, linking the selected branch to view via the Repository Browser.
The branch is displayed on the developer panel and is also associated to the mentioned Jira issue by fulfilling one of the following conditions:
TEST-1 fixed binaries.
TST-1-new-branchbranch will be visible on the developer panel of the TST-1 issue page even if the
TST-1-new-branchbranch has just been forked from master and does not have any new commit.
Clickto create a branch for the selected repository. The following dialog is displayed:
Select Repository. Set Base branch and Branch name then click Create branch to proceed. The newly created branch is listed under the Branches section based on branch name. The index operation starts immediately after the branch is created.
Hover the mouse pointer on the branch label to reveal the Delete icon. Click this icon to remove the created branch from the Branch list. This action will also delete it from the repository in which it was created.
The numbers ahead and behind represent the number of commits that are ahead/behind the main branch:
Clicking on the branch text links will open that issue in the Repository Browser. If Repository Browser is disabled for this repository, the text links will be inactive.
The Merge requests (if GitLab is connected) or Pull Requests (GitHub connected git hosts) section lists the merge/pull requests and their status. All merge/pull requests from all types of sources are shown here (for now, GitLab and GitHub).
The displayed information depends on which supported git hosts are connected to Jira. For example:
For necessary permissions that GitLab users must have for creating branches/merge requests, see GitLab Documentation: Permissions
For example, if GitLab is connected to Jira, create a merge request by clicking Create merge request. The following dialog is displayed:
Select Repository. Set Source branch and Target branch. Enter a Title name for this merge request then click Create. The newly created merge request is listed under the Merge requests section.
If you want to create a pull request for GitHub, click Create pull request.
The merge/pull request is displayed on the developer panel and will also be associated to the mentioned Jira issue by fulfilling one of the following conditions:
This will also allow a service user to associate a Merge/Pull Request with multiple Jira issues regardless of commit associations.
BigBrassBand recommends service users to enable pull/merge requests webhook trigger events. This way, any changes to merge/pull requests gets reindexed quickly.
The Merge/Pull Request list provides status information about the merge/pull request if it is opened or merged. For example:
Hover the mouse pointer on the merge/request label to see information of the repository and branch it belongs to:
In Issue and Search pages, the developer panel is visible on the right pane:
In Jira Agile screen, click on an issue on the board grid. Scroll down on the right pane to view the developer panel: