How to work with Branches

How to create a branch for this Issue on Git Provider site

  1. Make sure that the repository you are creating a branch in is registered in the system. The administrator of your Jira instance is able to provide this information.

  2. In order to link branch to Jira Issue, the branch name has to contain the Issue key. It doesn’t have to be Issue key exclusively, just to be somewhere in the branch name.

Branches popup

Please note that branches are located by their names. If there are commits in a branch that contains Issue key in their message, the plugin will not update them.

On the other hand, the Last Update does track the time of the last update made in this branch. If you wish to have both commits and branches visible please put the Issue key in every entity you want to have updated. 

  1. Repository of this branch. It is a link to the Git Provider site should you need more information.

  2. Name of this branch. It is a link to the Git Provider site.

  3. Time of the last update (i.e. - time of the last commit made to this branch).

  4. You can request a merge of this branch.

  5. This branch is identical to master and is considered merged.

Branch naming

The same logic applies to commit message.

1. The branch name doesn’t have to be the Issue key exclusively. It may contain other information and it will still be detected by Integration App.


Updated branches popup 

In this screenshot, you can see that branches are updated and a new one is added.

Please note that "feature-branch" contains new commit and therefore is not considered merged.

  1. New branch is loaded which contains new commit.

  2. Old branch still points on master.