GitHub Enterprise Server

Integrate GitHub Enterprise Server with Jira Data Center/Server

Quickly learn how to connect GitHub Enterprise Server git repositories via Git Integration for Jira Server.

What’s on this page:

• Integrate GitHub Enterprise Server with Jira Data Center/Server
  • Creating a personal access token
  • Using Full feature integration
  • Single repository (Manual integration)
  • Setting up GitHub Enterprise Server permissions
  • Default repository permission**
  • Teams and collaborators
  • Setting up GitHub web links
  • Viewing git commits in Jira Server
  • Require User PAT settings for user access
  • Working with branches and pull requests
  • Default branch
  • Creating branches
  • Creating pull requests
  • How to enable GetRepositories log response from GitHub to the Jira log?
  • More Integration Guides

Creating a personal access token

While instructions from GitHub works just fine, follow this article for some specific instructions to get you started.

VERSION 4.27+
There will be two new options now available in the GIJ General Settings. Enabling these settings requires an “extended” scope for your PATs.

To utilize the new GitHub share PR events, we recommend that users must update their personal access token to have the following scopes:

• read:discussion
• read:org
• read:user
• repo (all)
• user:email

Using Full feature integration

This process requires an existing GitHub Enterprise account.

We recommend using the Add new integration panel to connect multiple repositories from your GitHub Enterprise Server account.

This setup uses full feature integration offering functions and features not found on single repository connections.

1. On your Jira Server dashboard menu, go to Git ➜ Manage repositories. The git configuration page for connecting repositories is displayed.

2. On the Add new integration panel, click GitHub Enterprise. The Add new integration Wizard is displayed.

   
   

   • For the Host URL, enter the address of the GitHub Enterprise server.

   • Enter the Personal Access Token in the provided box as required.

     Note: For repository managers, collaborators or users that have enabled 2FA, enter username and the PAT as the password.

   • Configuring the Advanced settings is optional. However, admins/power users may set how the project listing is displayed.

     
     

     • Custom API Path  –  his is a relative path that starts with “/”.  The maximum allowed length is 2000 characters or less. The integration will use the relative REST API path to retrieve the list of tracked repositories. The Custom API Path is called everytime the list of repositories is loaded, on a regular scheduled reindex and a manual reindex.

       For more examples, see article Jira Server: Working with Custom API Path – GitHub Enterprise.

     • JMESPath filter  –  JMESPath is a query language for JSON used to filter API results and to limit which repositories are integrated. The maximum allowed length is 2000 characters or less.

       For help with writing expressions, please contact support. Read about JMESPath expressions on their website.

       For some other examples, see Working with JMESPath Filter in GitHub Enterprise.

     • Fetch refspec  –  Git refspecs contains patterns mapped as references from the remote to the local repository.
       For more information, see Git Internals — The Refspec.

       • The first two refspec options are required.

       • The rest of the options are OPTIONAL:

         • Clone and index ref notes (refs/notes) – This is a reference to refs/notes/* used for fetching. This option is enabled by default. This affects git notes which are not shown:

           • …when refs/notes are disabled on connecting a repository.
           • …when a new note comes when refs/notes is disabled.

         • Clone and index changes (refs/changes) – This is a reference to refs/changes/* used for fetching.  This option is turned off by default.

         • Clone and index other refs – This is a user-defined list of references used for fetching.  It is a comma-separated list with the format:

           • +refs/refname1/*:refs/refname1/*, refs/refname2/*:refs/refname2/*, …

   While Custom API Path and JMESPath filter are mutually exclusive, you can use one, the other, both or neither.

3. Click Connect.

4. On the following screen, the Git Integration for Jira app will read all available repositories from your GitHub Enterprise Server account. Click Import repositories.

   • Repositories that are added or removed from GitHub Enterprise Server will be likewise connected or disconnected from Jira Server.

   • If your git url contains multiple repositories, it will be added as tracked repositories in the git configuration list. Otherwise, a git repository is added instead.

5. After the import process, the Settings dialog is displayed:

   
   

   • On the Integration Settings, setting the Require User PAT option to ON, will require users to provide PAT specific for branch and merge requests (via the developer panel on the Jira issue page). For more information on this feature, see Integration Settings: Require User PAT.

   • Set Smart commits and Repository Browser to enable/disable these features.

   • Set Project Permissions according to your organization’s project association rules. For detailed information, see Associating project permissions.

6. Click Finish to complete this setup.

GitHub Enterprise Server repositories are now connected to Jira Server.

Single repository (Manual integration)

This process requires an existing GitHub Enterprise Server git repository. Look for the git clone URL on the repository project page.

Choose between SSH or HTTPS. Use this information to connect the GitLab git repository to your Jira server via Git Integration for Jira app.

1. On your Jira dashboard menu, go to Git ➜ Manage repositories.

2. Click Connect to Git Repository (or click the Git icon on the Add new integration panel) to open the Connect Wizard.

3. Paste the URL from GitHub Enterprise Server web portal in the provided box.

4. Continue to the next step by following the screen instructions.

5. Click Finish to complete this process. 

The repository is now connected to Jira Server.

Setting up GitHub Enterprise Server permissions

We recommend using a “service user” in GitHub Enterprise (example: GitIntegrationforJira) to be used to integrate with Git Integration for Jira app. This dedicated “service user” will allow the GitHub Enterprise Server administrator to set permissions so the app clones only the desired repositories.

Assign GitHub Enterprise Server permissions for team members or collaborators to allow which resources are accessible for service users. This feature is only available in a GitHub Organization.

Default repository permission**

1. Login to your GitHub Enterprise Server account.

2. Go to  Profile ➜ Settings.

3. Under Organization settings, click Member Privileges.

   
   

   • Choose the default permission level for organization members.

   • The default repository permission only applies to organization members and not to outside collaborators. If the default permission is set to None, organization members will need to be given access to repositories using the Teams or Collaborators methods (see below).

4. Save the changes.

For more information, see Access Permissions on GitHub ».

Teams and collaborators

To give a member additional access, they must be added to a team or make them collaborators on individual repositories.

Set default repository permission for the current team:

1. Open an organization team. (Your org ➜ Team ➜ scroll down to the bottom then click the desired team.)

2. Click the Repositories tab.

   
   

3. Set Read, Write or Admin repository access as desired.

Assign members to a team on your GitHub repository:

1. Create a team in your GitHub Organization.

2. Invite a member to add it into the team.  An email invitation is sent to that GitHub service user.

   
   

   The service user is then added to the team if the invitation has been accepted.

3. Click the service user to manage permissions for this member to:

   • Set desired Role for this member.

   • Convert this member to outside collaborator.

   • Give this member access to organization repositories.

   • Remove this member from the team.

4. Click Manage access to manage repository access for this member.

For more information on organization teams, see GitHub: Organizing Members into Teams ».

For more information on inviting collaborators, see Inviting Collaborators to a Personal/Organization Repository ».

Setting up GitHub web links

The Git Integration for Jira app automatically configures web linking for GitHub Enterprise Server git repositories.

For single repository connections, web link setup is optional. However, git links will become available in Git Commits tab when configured.

For more information on this feature, see Documentation: Web linking.

Viewing git commits in Jira Server

1. Perform a git commit by adding the Jira issue key in the commit message. This will associate the commit to the mentioned Jira issue.

2. Open the Jira issue.

3. Scroll down to the Activity panel then click the Git Commits tab.

4. Click View full commit to view the code diff.

For more information about this feature, see Documentation: Viewing commit code diffs.

Require User PAT settings for user access

For teams looking to maintain user attribution, Jira administrators can place a requirement where individual Jira users must provide personal access tokens to perform certain actions. This includes actions such as creating a branch or pull request in Jira using their git service account – rather than the integration account.

For more information, see Require personal access tokens for user access.

If the Require User PAT option is enabled in the Integration Feature Settings and a user PAT isn’t configured yet for the selected repository via Repository Browser, a text label about setting up your PAT is displayed on the create branch and create pull/merge request dialogs.

Click this text label to open the Setup PAT dialog and paste your personal access token in the provided box. Click Update.

The Setup PAT dialog is also accessible via Repository Browser (dashboard menu Git ➜ Repository browser) ➜ Click the icon under Pers. Access column.

Working with branches and pull requests

This process requires a GitHub Enterprise Server git repository and a PAT with repo scopes.

For GitHub Organization, the user must have the Write permissions and the repo PAT scopes.

Default branch

Most git integrations allow changing of the default branch of the repository/project other than “master”. This change is reflected in the Repository Settings of the Git Integration for Jira app on the next reindex. Auto-connected integrations support this feature where Git Integration for Jira app gets the default branch from almost all integrations and apply this setting at repository level.

Creating branches

On your Jira Server, open a Jira issue. On the Jira developer panel under Git Integration, click Create branch. The following dialog is displayed.

Pointers:

1. Select a Repository from the list.

   • If there are several repositories with the same name, the listed GitHub repositories will have their names attached with a GitHub organization name. For example, BigBrassBand/second-webhook-test-repo.

   • Use the search box to look for the specific repository that will be used.

2. Choose a Base branch.

3. Enter a Branch name or leave it as is (recommended).

The newly-created branch is now listed in the developer panel under Branches. Perform a commit to the newly-created branch to be ready for merge.

Creating pull requests

The pull request feature works the same as merge request. On your Jira Server, open the Jira issue where your previously created a branch. On the developer panel under Git Integration, click Create pull request. The following dialog is displayed.

Pointers:

1. Select a Repository from the list.

   • If there are several repositories with the same name, the listed GitHub repositories will have their names attached with a GitHub organization name. For example, BigBrassBand/second-webhook-test-repo.

   • Use the search box to look for the specific repository that will be used.

2. Choose the newly-created branch as the Source branch.

3. Set master as the Target branch.

4. 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 GitHub web portal.

How to enable GetRepositories log response from GitHub to the Jira log?

1. Open Jira System Administration then click Logging and profiling on the left sidebar.

2. Under the Default loggers section, click Configure….

3. Set the Package name to com.bigbrassband.jira.git.services.integration.

4. Set Logging Level to DEBUG.

5. Click Add to proceed.

IMPORTANT! Remember to turn this setting off after you have obtained the log file for analysis.

More Integration Guides

GitHub.com (Git Integration for Jira Data Center/Server)

GitHub Enterprise Server (this page)

GitHub App integration (Git Integration for Jira Data Center/Server)

GitLab.com (Git Integration for Jira Data Center/Server)

GitLab CE/EE (Git Integration for Jira Data Center/Server)

Azure DevOps | Visual Studio Team Services (VSTS) (Git Integration for Data Center/Jira Server)

Azure DevOps Server | Team Foundation Services (TFS) (Git Integration for Jira Data Center/Server)

AWS CodeCommit (Git Integration for Jira Data Center/Server)

Gerrit (Git Integration for Jira Data Center/Server)

Bitbucket Server (Git Integration for Jira Data Center/Server)

Bonobo (Git Integration for Jira Data Center/Server)

Windows Network | Server Share (Git Integration for Jira Data Center/Server)

Tracked Folders (Git Integration for Jira Data Center/Server)

Back to: Integration basics (Git Integration for Jira Data Center/Server)