Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Commit b6a88ea

Browse files
committed
GIT-6062 Add support info
1 parent 19eaec7 commit b6a88ea

File tree

2 files changed

+249
-232
lines changed

2 files changed

+249
-232
lines changed

‎git-integration-for-jira-self-managed/GitHub-Enterprise-Server-gij-self-managed.md

Lines changed: 127 additions & 112 deletions
Original file line numberDiff line numberDiff line change
@@ -53,11 +53,12 @@ Quickly learn how to connect GitHub Enterprise Server git repositories via Git I
5353
**What's on this page:**
5454
- [Integrate GitHub Enterprise Server with Jira Data Center/Server](#integrate-github-enterprise-server-with-jira-data-centerserver)
5555
- [Creating a personal access token](#creating-a-personal-access-token)
56-
- [Using Full feature integration](#using-full-feature-integration)
57-
- [Single repository (Manual integration)](#single-repository-manual-integration)
5856
- [Setting up GitHub Enterprise Server permissions](#setting-up-github-enterprise-server-permissions)
5957
- [Default repository permission\*\*](#default-repository-permission)
6058
- [Teams and collaborators](#teams-and-collaborators)
59+
- [Integration platform support](#integration-platform-support)
60+
- [Using Full feature integration](#using-full-feature-integration)
61+
- [Single repository (Manual integration)](#single-repository-manual-integration)
6162
- [Setting up GitHub web links](#setting-up-github-web-links)
6263
- [Viewing git commits in Jira Server](#viewing-git-commits-in-jira-server)
6364
- [Require User PAT settings for user access](#require-user-pat-settings-for-user-access)
@@ -111,6 +112,130 @@ To utilize the new GitHub share PR events, we recommend that users must update t
111112

112113
 
113114

115+
### Setting up GitHub Enterprise Server permissions
116+
117+
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.
118+
119+
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.
120+
121+
 
122+
123+
#### Default repository permission**
124+
125+
1. Login to your GitHub Enterprise Server account.
126+
127+
2. Go to ![profile icon](/wp-content/uploads/gij-profile-icon.png) Profile ➜ **Settings**.
128+
129+
3. Under _Organization settings_, click **Member Privileges**.
130+
131+
![](/wp-content/uploads/gij-github-default-repo-permission-c.png)
132+
* Choose the default permission level for organization members.
133+
134+
* 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).
135+
136+
4. **Save** the changes.
137+
138+
139+
For more information, see **Access Permissions on GitHub »**.
140+
141+
 
142+
143+
#### Teams and collaborators
144+
145+
To give a member additional access, they must be added to a team or make them collaborators on individual repositories.
146+
147+
<br>
148+
149+
**Set default repository permission for the current team:**
150+
151+
1. Open an organization team. (_Your org ➜ Team ➜ scroll down to the bottom then click the desired team._)
152+
153+
2. Click the **Repositories** tab.
154+
155+
![](/wp-content/uploads/gij-github-manage-repo-permission-tab-c.png)
156+
157+
3. Set **Read**, **Write** or **Admin** repository access as desired.
158+
159+
<br>
160+
161+
**Assign members to a team on your GitHub repository:**
162+
163+
1. Create a team in your GitHub Organization.
164+
165+
2. Invite a member to add it into the team. An email invitation is sent to that GitHub service user.
166+
167+
![](/wp-content/uploads/gij-add-members-to-team-c.png)
168+
169+
The service user is then added to the team if the invitation has been accepted.
170+
171+
3. Click the service user to manage permissions for this member to:
172+
173+
* Set desired **Role** for this member.
174+
175+
* Convert this member to outside collaborator.
176+
177+
* Give this member access to organization repositories.
178+
179+
* Remove this member from the team.
180+
181+
4. Click **Manage access** to manage repository access for this member.
182+
183+
184+
![](/wp-content/uploads/gij-manage-team-repo-permission.png)
185+
186+
<div class="bbb-callout bbb--note">
187+
<div class="irow">
188+
<div class="ilogobox">
189+
<span class="logoimg"></span>
190+
</div>
191+
<div class="imsgbox">
192+
While users have configured PAT for repository access, users in a GitHub Enterprise Server must at least have <b>Read</b> permissions. This allows them to view commits and smart commits, and browse repositories (if enabled) of connected GitHub Enterprise Server repositories inside Jira.
193+
</div>
194+
</div>
195+
</div>
196+
197+
<div class="bbb-callout bbb--info">
198+
<div class="irow">
199+
<div class="ilogobox">
200+
<span class="logoimg"></span>
201+
</div>
202+
<div class="imsgbox">
203+
For repository managers, collaborators and commit authors, set these users to have <b>Write</b> permissions. This will allow them to view commits and smart commits, browse repositories and also enables them to create branches and pull requests to specified GitHub git repositories via developer panel of a Jira issue.
204+
</div>
205+
</div>
206+
</div>
207+
208+
<div class="bbb-callout bbb--alert">
209+
<div class="irow">
210+
<div class="ilogobox">
211+
<span class="logoimg"></span>
212+
</div>
213+
<div class="imsgbox">
214+
The user PAT for "Require User PAT" setting should have <b>Write</b> permission. Otherwise, the user will not be able to use it for branch or pull request creation/deletion.
215+
</div>
216+
</div>
217+
</div>
218+
219+
For more information on organization teams, see [**GitHub: Organizing Members into Teams »**](https://docs.github.com/en/organizations/organizing-members-into-teams).
220+
221+
For more information on inviting collaborators, see [**Inviting Collaborators to a Personal/Organization Repository »**](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository).
222+
223+
&nbsp;
224+
225+
### Integration platform support
226+
227+
GitHub supports the four most recent version releases. We follow this direction and the Git Integration for Jira app (GIJ) will also support these versions.
228+
229+
For previous versions, GIJ supports the following GHE versions:
230+
* GitHubEE 3.11 (Deprecation 2024年12月05日)
231+
* GitHubEE 3.10 (Deprecation 2024年08月29日)
232+
* GitHubEE 3.9 (Deprecation 2024年06月29日)
233+
* GitHubEE 3.8 (Deprecation 2024年03月07日)
234+
235+
GHE 3.8 supports authenticating with username and password. Therefore, GIJ will also do.
236+
237+
&nbsp;
238+
114239
### Using Full feature integration
115240

116241
This process requires an existing GitHub Enterprise account.
@@ -223,116 +348,6 @@ The repository is now connected to Jira Server.
223348

224349
&nbsp;
225350

226-
### Setting up GitHub Enterprise Server permissions
227-
228-
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.
229-
230-
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.
231-
232-
&nbsp;
233-
234-
#### Default repository permission**
235-
236-
1. Login to your GitHub Enterprise Server account.
237-
238-
2. Go to ![profile icon](/wp-content/uploads/gij-profile-icon.png) Profile ➜ **Settings**.
239-
240-
3. Under _Organization settings_, click **Member Privileges**.
241-
242-
![](/wp-content/uploads/gij-github-default-repo-permission-c.png)
243-
* Choose the default permission level for organization members.
244-
245-
* 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).
246-
247-
4. **Save** the changes.
248-
249-
250-
For more information, see **Access Permissions on GitHub »**.
251-
252-
&nbsp;
253-
254-
#### Teams and collaborators
255-
256-
To give a member additional access, they must be added to a team or make them collaborators on individual repositories.
257-
258-
<br>
259-
260-
**Set default repository permission for the current team:**
261-
262-
1. Open an organization team. (_Your org ➜ Team ➜ scroll down to the bottom then click the desired team._)
263-
264-
2. Click the **Repositories** tab.
265-
266-
![](/wp-content/uploads/gij-github-manage-repo-permission-tab-c.png)
267-
268-
3. Set **Read**, **Write** or **Admin** repository access as desired.
269-
270-
<br>
271-
272-
**Assign members to a team on your GitHub repository:**
273-
274-
1. Create a team in your GitHub Organization.
275-
276-
2. Invite a member to add it into the team. An email invitation is sent to that GitHub service user.
277-
278-
![](/wp-content/uploads/gij-add-members-to-team-c.png)
279-
280-
The service user is then added to the team if the invitation has been accepted.
281-
282-
3. Click the service user to manage permissions for this member to:
283-
284-
* Set desired **Role** for this member.
285-
286-
* Convert this member to outside collaborator.
287-
288-
* Give this member access to organization repositories.
289-
290-
* Remove this member from the team.
291-
292-
4. Click **Manage access** to manage repository access for this member.
293-
294-
295-
![](/wp-content/uploads/gij-manage-team-repo-permission.png)
296-
297-
<div class="bbb-callout bbb--note">
298-
<div class="irow">
299-
<div class="ilogobox">
300-
<span class="logoimg"></span>
301-
</div>
302-
<div class="imsgbox">
303-
While users have configured PAT for repository access, users in a GitHub Enterprise Server must at least have <b>Read</b> permissions. This allows them to view commits and smart commits, and browse repositories (if enabled) of connected GitHub Enterprise Server repositories inside Jira.
304-
</div>
305-
</div>
306-
</div>
307-
308-
<div class="bbb-callout bbb--info">
309-
<div class="irow">
310-
<div class="ilogobox">
311-
<span class="logoimg"></span>
312-
</div>
313-
<div class="imsgbox">
314-
For repository managers, collaborators and commit authors, set these users to have <b>Write</b> permissions. This will allow them to view commits and smart commits, browse repositories and also enables them to create branches and pull requests to specified GitHub git repositories via developer panel of a Jira issue.
315-
</div>
316-
</div>
317-
</div>
318-
319-
<div class="bbb-callout bbb--alert">
320-
<div class="irow">
321-
<div class="ilogobox">
322-
<span class="logoimg"></span>
323-
</div>
324-
<div class="imsgbox">
325-
The user PAT for "Require User PAT" setting should have <b>Write</b> permission. Otherwise, the user will not be able to use it for branch or pull request creation/deletion.
326-
</div>
327-
</div>
328-
</div>
329-
330-
For more information on organization teams, see [**GitHub: Organizing Members into Teams »**](https://docs.github.com/en/organizations/organizing-members-into-teams).
331-
332-
For more information on inviting collaborators, see [**Inviting Collaborators to a Personal/Organization Repository »**](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository).
333-
334-
&nbsp;
335-
336351
### Setting up GitHub web links
337352

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

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /