From 3bd0c6ee3d58224548cd5bd82fb1c2cca92b752a Mon Sep 17 00:00:00 2001 From: Roberto Vizcarra Date: 2022年6月15日 15:18:29 -0700 Subject: [PATCH 1/3] Linking/Formatting --- ...r-for-self-hosted-git-servers-gij-cloud.md | 5 +- .../create-branch-gij-cloud.md | 16 +++---- .../create-pull-or-merge-request-gij-cloud.md | 14 +++--- ...nches-and pull-merge-requests-gij-cloud.md | 6 +-- ...ggers-for-a-single-repository-gij-cloud.md | 6 +-- ...eating-personal-access-tokens-gij-cloud.md | 2 +- ...nking-to-the-gitkraken-client-gij-cloud.md | 2 +- .../default-branch-feature-gij-cloud.md | 4 +- .../default-repository-feature-gij-cloud.md | 4 +- .../developer-gij-cloud.md | 2 +- ...development-information-views-gij-cloud.md | 22 ++++----- .../development-panel-locations-gij-cloud.md | 1 - ...tatus-in-jira-issue-searching-gij-cloud.md | 1 - .../edit-integration-gij-cloud.md | 16 +++---- .../edit-repository-gij-cloud.md | 16 +++---- ...m-atlassian-for-smart-commits-gij-cloud.md | 48 ++++++++----------- ...er-integration-of-azure-repos-gij-cloud.md | 8 ++-- .../enable-beta-features-setting-gij-cloud.md | 2 +- ...ion-app-smart-commits-setting-gij-cloud.md | 6 +-- ...or-jira-and-workflow-triggers-gij-cloud.md | 4 +- ...and-workflow-triggers-setting-gij-cloud.md | 6 +-- ...-too-large-rejecting-the-pack-gij-cloud.md | 5 +- ...it-integration-for-jira-cloud-gij-cloud.md | 9 ++-- .../features-gij-cloud.md | 30 ++++++------ .../general-gij-cloud.md | 2 +- ...l-settings-for-administrators-gij-cloud.md | 17 ++++--- .../general-settings-gij-cloud.md | 30 ++++++------ .../generating-ssh-keys-gij-cloud.md | 5 +- .../gerrit-end-of-life-gij-cloud.md | 2 +- .../gerrit-gij-cloud.md | 4 +- ...-webhook-indexing-integration-gij-cloud.md | 3 +- ...ts-issue-tab-and-project-page-gij-cloud.md | 4 +- ...s-issue-tab-and-project-pages-gij-cloud.md | 2 +- .../git-commits-tab-gij-cloud.md | 3 +- ...ntegration-configuration-page-gij-cloud.md | 48 ++++++++----------- ...a-automation-template-library-gij-cloud.md | 2 +- ...-for-jira-cloud-release-notes-gij-cloud.md | 31 ++++++------ ...git-integration-for-jira-home-gij-cloud.md | 20 ++++---- ...-automation-advanced-examples-gij-cloud.md | 18 +++---- ...t-integration-jira-automation-gij-cloud.md | 8 ++-- ...ation-jira-cloud-video-guides-gij-cloud.md | 2 +- .../git-integration-options-gij-cloud.md | 38 +++++++-------- ...jira-cloud-feature-comparison-gij-cloud.md | 22 ++++++--- .../git-roll-up-issue-tab-gij-cloud.md | 3 +- ...git-roll-up-issue-tab-setting-gij-cloud.md | 4 +- .../git-roll-up-tab-gij-cloud.md | 6 +-- ...page-and-end-of-life-policies-gij-cloud.md | 10 ++-- .../git-tags-gij-cloud.md | 2 +- .../git-url-ports-gij-cloud.md | 5 +- .../git-user-identity-gij-cloud.md | 2 + .../github-com-gij-cloud.md | 24 +++++----- ...rise-jmespath-filter-examples-gij-cloud.md | 9 ++-- .../github-enterprise-eol-gij-cloud.md | 3 +- .../github-enterprise-server-gij-cloud.md | 28 +++++------ .../github-webhook-events-gij-cloud.md | 12 ++--- ...-webhook-indexing-integration-gij-cloud.md | 45 ++++++++--------- ...itkraken-integration-settings-gij-cloud.md | 4 +- ...tlab-ce-ee-eol-support-policy-gij-cloud.md | 3 +- .../gitlab-ce-ee-gij-cloud.md | 36 +++++++------- .../gitlab-com-gij-cloud.md | 28 +++++------ ...e-ee-jmespath-filter-examples-gij-cloud.md | 15 ++---- .../gitlab-webhook-events-gij-cloud.md | 1 + ...-webhook-indexing-integration-gij-cloud.md | 44 ++++++++--------- .../glossary-of-terms-gij-cloud.md | 4 +- .../hooks-and-webhooks-gij-cloud.md | 6 +-- ...-jira-development-information-gij-cloud.md | 2 +- ...or-jira-and-workflow-triggers-gij-cloud.md | 5 +- ...a-app-pricing-after-the-trial-gij-cloud.md | 3 +- .../how-to-articles-gij-cloud.md | 40 ++++++++++------ .../how-to-calculate-pricing-gij-cloud.md | 3 +- ...ggers-for-a-single-repository-gij-cloud.md | 3 +- .../how-to-get-a-quote-gij-cloud.md | 3 +- ...link-branches-to-a-jira-issue-gij-cloud.md | 3 +- ...pull-requests-to-a-jira-issue-gij-cloud.md | 17 +++---- ...erge-requests-to-a-jira-issue-gij-cloud.md | 3 +- ...ng-triggers-formerly-webhooks-gij-cloud.md | 8 ++-- .../indexing-triggers-gij-cloud.md | 33 +++++-------- .../initial-setup-guide-gij-cloud.md | 16 +++---- .../installation-and-setup-gij-cloud.md | 1 - ...ion-via-atlassian-marketplace-gij-cloud.md | 2 +- .../integration-guide-gij-cloud.md | 20 ++++---- 81 files changed, 455 insertions(+), 497 deletions(-) diff --git a/git-integration-for-jira-cloud/connection-error-for-self-hosted-git-servers-gij-cloud.md b/git-integration-for-jira-cloud/connection-error-for-self-hosted-git-servers-gij-cloud.md index 99bbd84..97f321c 100644 --- a/git-integration-for-jira-cloud/connection-error-for-self-hosted-git-servers-gij-cloud.md +++ b/git-integration-for-jira-cloud/connection-error-for-self-hosted-git-servers-gij-cloud.md @@ -14,14 +14,13 @@ Jira admins are not able to connect Jira Cloud to self-hosted git servers when h Jira admins will see a message similar to the one below when connecting to self-hosted git servers hosted behind a firewall or otherwise not reachable. -| | -| --- | | **Error** | +| --- | | ```java
com.bigbrassband.gitforjiracloud.appserver.apiendpoint.tasks.TaskException: com.bigbrassband.gitforjiracloud.indexer.sources.TrackedGitLabRepoException: Can not connect to GitLab server
at com.bigbrassband.gitforjiracloud.appserver.apiendpoint.tasks.Task.runWithMappedExceptions(Task.java:56)
at com.bigbrassband.gitforjiracloud.appserver.apiendpoint.ApiEndPoint.runTasks(ApiEndPoint.java:162)
at com.bigbrassband.gitforjiracloud.appserver.apiendpoint.ApiEndPoints.handleRequest(ApiEndPoints.java:79)
at com.bigbrassband.gitforjiracloud.appserver.AppServer$SuperHandler.handle(AppServer.java:219)
at com.bigbrassband.common.util.httpplumbing.WebServer$InternalRequestHandler.handle(WebServer.java:164)
at org.apache.http.protocol.HttpService.doService(HttpService.java:437)
at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:342)
at com.bigbrassband.common.util.httpplumbing.Worker.run(Worker.java:41)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.bigbrassband.gitforjiracloud.indexer.sources.TrackedGitLabRepoException: Can not connect to GitLab server
at com.bigbrassband.gitforjiracloud.indexer.sources.GitlabApiMonster.getGitlabApi(GitlabApiMonster.java:34)
at com.bigbrassband.gitforjiracloud.indexer.sources.GitlabRepoSource.getRepositories(GitlabRepoSource.java:47)
at com.bigbrassband.gitforjiracloud.appserver.apiendpoint.tasks.git.repos.PingRepoTask.pingRepoSource(PingRepoTask.java:91)
at com.bigbrassband.gitforjiracloud.appserver.apiendpoint.tasks.git.repos.PingRepoTask.run(PingRepoTask.java:71)
at com.bigbrassband.gitforjiracloud.appserver.apiendpoint.tasks.Task.runWithMappedExceptions(Task.java:36)
... 12 more
Caused by: org.gitlab.api.GitlabAPIException
at org.gitlab.api.http.GitlabHTTPRequestor.handleAPIError(GitlabHTTPRequestor.java:543)
at org.gitlab.api.http.GitlabHTTPRequestor.to(GitlabHTTPRequestor.java:201)
at org.gitlab.api.http.GitlabHTTPRequestor.to(GitlabHTTPRequestor.java:167)
at org.gitlab.api.GitlabAPI.getVersion(GitlabAPI.java:3199)
at org.gitlab.api.GitlabAPI.createPATAuthOnly(GitlabAPI.java:158)
at org.gitlab.api.GitlabAPI.create(GitlabAPI.java:145)
at com.bigbrassband.gitforjiracloud.indexer.sources.GitlabApiMonster.getGitlabApi(GitlabApiMonster.java:29)
... 16 more
Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')

``` | ## Solution -See [Whitelist BigBrassBand Cloud](/git-integration-for-jira-cloud/allow-list-whitelist-bigbrassband-cloud/). +See [Whitelist BigBrassBand Cloud](/git-integration-for-jira-cloud/allow-list-whitelist-bigbrassband-cloud-gij-cloud). **Contact Us** diff --git a/git-integration-for-jira-cloud/create-branch-gij-cloud.md b/git-integration-for-jira-cloud/create-branch-gij-cloud.md index e0e142a..3dcc07b 100644 --- a/git-integration-for-jira-cloud/create-branch-gij-cloud.md +++ b/git-integration-for-jira-cloud/create-branch-gij-cloud.md @@ -11,8 +11,8 @@ taxonomy: **Jira administrator notes** -* Jira users can now provide their own personal access tokens (PAT) even if they are not required/mandated by the Jira admin. See [Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request/) for instructions on how to configure this feature. -* The **View developer tools** _permission_ is required to view the Source Code panel (see more in [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel/). Jira users must also have the **Browse Project** _permissions_ to a project associated with a repository to view. +* Jira users can now provide their own personal access tokens (PAT) even if they are not required/mandated by the Jira admin. See [Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request-gij-cloud) for instructions on how to configure this feature. +* The **View developer tools** _permission_ is required to view the Source Code panel (see more in [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel-gij-cloud). Jira users must also have the **Browse Project** _permissions_ to a project associated with a repository to view. * Creating branch feature can be disabled for all Jira users (regardless of permissions) in General settings @@ -28,7 +28,7 @@ The Create branch feature offers Jira users the ability to create a git branch d ![](https://bigbrassband.atlassian.net/wiki/download/attachments/733282366/gitcloud-create-branch-dlg.png?version=1&modificationDate=1635931446719&cacheVersion=1&api=v2) -For information about creating pull/merge requests from a Jira issue - see [Create pull or merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request/). +For information about creating pull/merge requests from a Jira issue - see [Create pull or merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud). ## **Advantages** @@ -36,7 +36,7 @@ When creating a branch from within Jira: * Automatically populates branch name with issue key (necessary for branch ↔ issue association) and issue summary. * Further - default branch naming conventions can be customized to match your development workflow. For example: `${issuetype:New Issue,new,Bug Fix,bug}/${issuekey}-${summary}` generates "`bug/PRJ-123-add-more-logging`" (See General settings for more information). -* Require each Jira user to provide their Personal Access Token for creating branches. This option adds some friction to creating branches/pull requests but enabling this setting will enforce the git server user permissions as well as give better attribution for the actions. See [Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request/) for more information. +* Require each Jira user to provide their Personal Access Token for creating branches. This option adds some friction to creating branches/pull requests but enabling this setting will enforce the git server user permissions as well as give better attribution for the actions. See [Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request-gij-cloud) for more information. * Each Jira user can set a **Default repository** for the current Jira project. (See User settings for more information). @@ -59,15 +59,15 @@ When creating a branch from within Jira: ## **Steps to creating a git branch in Jira** -1. **Prerequisite:** Jira administrator configures a Full feature integration in the Git Integration for Jira Cloud app. See [Integration Guide](/git-integration-for-jira-cloud/Integration-Guide) for more information. +1. **Prerequisite:** Jira administrator configures a Full feature integration in the Git Integration for Jira Cloud app. See [Integration Guide](/git-integration-for-jira-cloud/integration-guide-gij-cloud) for more information. 2. To access the Create branch action - do one of the following: 1. Enable the **Git Development panel** or - 2. Open the [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel/) + 2. Open the [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel-gij-cloud) 3. Click **Create branch** in one of the panels from step 2. 4. Select git repository. - 1. Optional: designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/User-Settings) page. + 1. Optional: designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. 2. Use the search box to look for the specific name of the repository that will be used. -5. If a [personal access token is required](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request/) (and not yet provided) - follow on screen instructions to provide a [personal access token](/git-integration-for-jira-cloud/creating-personal-access-tokens/) with correct permissions for selected repository. +5. If a [personal access token is required](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request-gij-cloud) (and not yet provided) - follow on screen instructions to provide a [personal access token](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud) with correct permissions for selected repository. 6. Select base branch. 7. Verify branch name is correct. Edit as desired. Note: the Jira issue key must remain in the branch name to create the branch ↔ Jira issue association. 8. Click **Create branch**. diff --git a/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud.md b/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud.md index 3a8a03b..cbdefdf 100644 --- a/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud.md +++ b/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud.md @@ -10,8 +10,8 @@ taxonomy: **Jira administrator notes** -* Jira users can be required to provide their own Personal Access Token when creating a branch or pull request. See [Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request/) for instructions on how to configure this feature. -* The **View developer tools** _permission_ is required to view the Source Code panel (see more in [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel/)). Jira users must also have the **Browse Project** _permissions_ to a project associated with a repository to view. +* Jira users can be required to provide their own Personal Access Token when creating a branch or pull request. See [Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request-gij-cloud) for instructions on how to configure this feature. +* The **View developer tools** _permission_ is required to view the Source Code panel (see more in [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel-gij-cloud)). Jira users must also have the **Browse Project** _permissions_ to a project associated with a repository to view. * Creating pull/merge request feature can be disabled for all Jira users (regardless of permissions) in General settings. @@ -32,14 +32,14 @@ The **Create pull request** feature offers Jira users the ability to create a gi ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/733315235/create-pull-request.png?version=2&modificationDate=1599320965937&cacheVersion=1&api=v2&width=933&height=349) -For information about creating a branch from a Jira issue - see [Create branch](/git-integration-for-jira-cloud/Create-branch). +For information about creating a branch from a Jira issue - see [Create branch](/git-integration-for-jira-cloud/create-branch-gij-cloud). ## **Advantages** When creating a pull request from within Jira: * Automatically populates the pull request title with issue key (necessary for pull request ↔ issue association) and issue summary. -* Require each Jira user to provide their Personal Access Token for creating pull requests. This option adds some friction to creating pull requests/branches but enabling this setting will enforce the git server user permissions as well as give better attribution for the actions. See [Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request/) for more information. +* Require each Jira user to provide their Personal Access Token for creating pull requests. This option adds some friction to creating pull requests/branches but enabling this setting will enforce the git server user permissions as well as give better attribution for the actions. See [Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request-gij-cloud) for more information. * Each Jira user can set a **Default repository** for the current Jira project. (See User settings for more information). @@ -62,15 +62,15 @@ When creating a pull request from within Jira: ## **Steps to creating a git pull request in Jira** -1. **Prerequisite:** Jira administrator configures a Full feature integration in the Git Integration for Jira Cloud app. See [Integration Guide](/git-integration-for-jira-cloud/Integration-Guide) for more information. +1. **Prerequisite:** Jira administrator configures a Full feature integration in the Git Integration for Jira Cloud app. See [Integration Guide](/git-integration-for-jira-cloud/integration-guide-gij-cloud) for more information. 2. To access the Create pull request action - do one of the following: 1. Enable the **Git Development panel** or - 2. Open the [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel/) + 2. Open the [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel-gij-cloud) 3. Click **Create pull request** in one of the panels from step 2. 4. Select git repository. 1. Optional: designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the **User settings** page. 2. Use the search box to look for the specific name of the repository that will be used. -5. If a [personal access token is required](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request/) (and not yet provided) - follow on screen instructions to provide a [personal access token](/git-integration-for-jira-cloud/creating-personal-access-tokens/) with correct permissions for selected repository. +5. If a [personal access token is required](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request-gij-cloud) (and not yet provided) - follow on screen instructions to provide a [personal access token](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud) with correct permissions for selected repository. 6. Select source branch. 7. Select target branch. 8. Verify pull request title is correct. Edit as desired. Note: the Jira issue key must remain in the pull request name to create the pull request ↔ Jira issue association. diff --git a/git-integration-for-jira-cloud/creating-branches-and pull-merge-requests-gij-cloud.md b/git-integration-for-jira-cloud/creating-branches-and pull-merge-requests-gij-cloud.md index cc97ec9..cafc060 100644 --- a/git-integration-for-jira-cloud/creating-branches-and pull-merge-requests-gij-cloud.md +++ b/git-integration-for-jira-cloud/creating-branches-and pull-merge-requests-gij-cloud.md @@ -6,7 +6,7 @@ taxonomy: category: git-integration-for-jira-cloud --- -The Git Integration for Jira app adds two features on the Jira issue developer panel – **Create branch**, and **Create pull/merge request**. For more information on where to access them, see the [Jira Git development panel documentation](https://bigbrassband.com/git-integration-for-jira/documentation/jira-developer-panel.html). +The Git Integration for Jira app adds two features on the Jira issue developer panel – **Create branch**, and **Create pull/merge request**. For more information on where to access them, see the [Jira Git development panel documentation](/git-integration-for-jira-cloud/jira-git-integration-development-panel-gij-cloud). Pull/merge requests are still indexed based on branch name even if the PR/MR title does not have the Jira issue key – as long as the branch name contains the Jira issue key. @@ -25,10 +25,10 @@ Main branch for repositories within an integration can only be changed on the gi Open a Jira issue then on the developer panel, click **Create Branch** label to create a branch for the selected repository. -For detailed information on this feature, see [Creating branches from Jira](/git-integration-for-jira-cloud/Create-branch). +For detailed information on this feature, see [Creating branches from Jira](/git-integration-for-jira-cloud/create-branch-gij-cloud). ## Creating pull/merge requests Open a Jira issue then on the developer panel, click **Create pull/merge request** label to create a pull/merge request for the selected repository. -For detailed information on this feature, see [Creating pull/merge requests from Jira](https://bigbrassband.atlassian.net/wiki/spaces/GITCLOUD/pages/733315235). \ No newline at end of file +For detailed information on this feature, see [Creating pull/merge requests from Jira](/git-integration-for-jira-cloud/creating-branches-and%20pull-merge-requests-gij-cloud) \ No newline at end of file diff --git a/git-integration-for-jira-cloud/creating-indexing-triggers-for-a-single-repository-gij-cloud.md b/git-integration-for-jira-cloud/creating-indexing-triggers-for-a-single-repository-gij-cloud.md index 40b7b73..7991c32 100644 --- a/git-integration-for-jira-cloud/creating-indexing-triggers-for-a-single-repository-gij-cloud.md +++ b/git-integration-for-jira-cloud/creating-indexing-triggers-for-a-single-repository-gij-cloud.md @@ -20,14 +20,12 @@ _**Optional headers:**_ * 'x-bbb-webhook-id' -- Can be any string representing the _id_ of the request to be used. -| | -| --- | | **Usage examples:** | +| --- | | ```java
curl -H 'x-bbb-webhook-type: push' -H 'content-type: application/json' -X POST -d @payload.json https://webhook/url
``` | | ```java
curl -H 'x-bbb-webhook-type: push' -H 'x-bbb-webhook-id: id-string' -H 'content-type: application/json' -X POST -d @payload.json https://webhook/url
``` | -| | -| --- | | **Payload.json** | +| --- | | ```java
{
"origin": "repository-origin"
}
``` | diff --git a/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud.md b/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud.md index 6d19980..5460c0d 100644 --- a/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud.md +++ b/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud.md @@ -63,7 +63,7 @@ If two-factor authentication is enabled for your GitLab account, you will need t While instructions from GitLab works just fine, here are some specific instructions to get you up and running: -1. Login to your GitLab account then go to your profile settings (menu ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Profile ➜ **Preferences**). +1. Login to your GitLab account then go to your profile settings (menu ➜ Profile ➜ **Preferences**). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/107216897/gitlab-user-profile-settings(c).png?version=2&modificationDate=1650862373604&cacheVersion=1&api=v2&width=262&height=327) 2. On the sidebar, click **Access Tokens**. diff --git a/git-integration-for-jira-cloud/deep-linking-to-the-gitkraken-client-gij-cloud.md b/git-integration-for-jira-cloud/deep-linking-to-the-gitkraken-client-gij-cloud.md index 94ab212..29249f9 100644 --- a/git-integration-for-jira-cloud/deep-linking-to-the-gitkraken-client-gij-cloud.md +++ b/git-integration-for-jira-cloud/deep-linking-to-the-gitkraken-client-gij-cloud.md @@ -40,7 +40,7 @@ Individual Jira Cloud users can enable or disable the GitKraken integration with ## Administrator settings -Jira Cloud administrators can disable or enable the GitKraken integration with Git Integration for Jira Cloud for all Jira users. All Jira Cloud users can enable the GitKraken integration separately (see [User settings](#User-settings) above). +Jira Cloud administrators can disable or enable the GitKraken integration with Git Integration for Jira Cloud for all Jira users. All Jira Cloud users can enable the GitKraken integration separately (see [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) above). Go to the Git Integration for Jira – **General settings** tab (sidebar). diff --git a/git-integration-for-jira-cloud/default-branch-feature-gij-cloud.md b/git-integration-for-jira-cloud/default-branch-feature-gij-cloud.md index 02312a4..74398fd 100644 --- a/git-integration-for-jira-cloud/default-branch-feature-gij-cloud.md +++ b/git-integration-for-jira-cloud/default-branch-feature-gij-cloud.md @@ -12,7 +12,7 @@ taxonomy: You can configure a default branch for a repository when creating new branches. This feature automatically sets the configured default branch for the selected repository each time you create new branches from a Jira issue. -Click ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Add default branch** to setup a default branch for the selected repository. The following dialog is displayed. +Click **Add default branch** to setup a default branch for the selected repository. The following dialog is displayed. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1958936625/gitcloud-user-settings-create-def-branch-dlg.png?version=2&modificationDate=1632842489171&cacheVersion=1&api=v2&width=442&height=245) @@ -26,6 +26,6 @@ Use this function to assign a branch for the selected repository: 1. Use the **Edit** or **Delete** options to make changes to the default branch configuration of the selected repository. -2. Click ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Add default branch** to add more default branch configuration for the selected repository. +2. Click **Add default branch** to add more default branch configuration for the selected repository. diff --git a/git-integration-for-jira-cloud/default-repository-feature-gij-cloud.md b/git-integration-for-jira-cloud/default-repository-feature-gij-cloud.md index 3ca1177..5cfca4d 100644 --- a/git-integration-for-jira-cloud/default-repository-feature-gij-cloud.md +++ b/git-integration-for-jira-cloud/default-repository-feature-gij-cloud.md @@ -7,7 +7,7 @@ taxonomy: --- -This feature allows users to set the default repository for a Jira project when using the [Create Branch](/git-integration-for-jira-cloud/Create-branch) and [Create pull/merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request/) features. +This feature allows users to set the default repository for a Jira project when using the [Create Branch](/git-integration-for-jira-cloud/create-branch-gij-cloud) and [Create pull/merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud) features. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1741094916/gitcloud-user-settings-default-repo-feature.png?version=1&modificationDate=1623726181829&cacheVersion=1&api=v2&width=680&height=332) @@ -25,7 +25,7 @@ On the **Repository** column, default repositories can be set using the dropdown ## Effect on branch and pull request dialogs -This configuration affects the [Create Branch](/git-integration-for-jira-cloud/create-branch/), [Create Pull Request](/git-integration-for-jira-cloud/create-pull-or-merge-request/) and [Create Merge Request](/git-integration-for-jira-cloud/create-pull-or-merge-request/) dialogs. +This configuration affects the [Create Branch](/git-integration-for-jira-cloud/create-branch-gij-cloud), [Create Pull or Merge Requests](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud). If no default repository is set, the **Create Branch** and **Create Pull/Merge Request** dialogs will allow users to select a repository and _**make it as default**_ by clicking the corresponding button. diff --git a/git-integration-for-jira-cloud/developer-gij-cloud.md b/git-integration-for-jira-cloud/developer-gij-cloud.md index d8eb664..83e56e0 100644 --- a/git-integration-for-jira-cloud/developer-gij-cloud.md +++ b/git-integration-for-jira-cloud/developer-gij-cloud.md @@ -60,4 +60,4 @@ The Git Integration for Jira Cloud app also supports multiple issue keys in a co Yes – the Git Integration for Jira Cloud app supports multiple Jira issue keys in a multiple-line commit message. -For more information, see **[Smart Commits »](/git-integration-for-jira-cloud/smart-commits-gij-cloud/)**. \ No newline at end of file +For more information, see **[Smart Commits »](/git-integration-for-jira-cloud/smart-commits-gij-cloud)**. \ No newline at end of file diff --git a/git-integration-for-jira-cloud/development-information-views-gij-cloud.md b/git-integration-for-jira-cloud/development-information-views-gij-cloud.md index 6e06df5..b1ae080 100644 --- a/git-integration-for-jira-cloud/development-information-views-gij-cloud.md +++ b/git-integration-for-jira-cloud/development-information-views-gij-cloud.md @@ -17,20 +17,14 @@ Atlassian Jira Cloud currently displays Jira Development Information in the Deve ![](https://bigbrassband.atlassian.net/wiki/download/attachments/643203115/f8e88373-1554-4f79-891b-3df44b2dbd60.png%3Fversion=1&modificationDate=1561212869840&cacheVersion=1&api=v2?version=1&modificationDate=1595588070927&cacheVersion=1&api=v2) -| | -| --- | -| ### **Detailed view of commits** | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/643203115/5761be45-4320-4e87-a843-20936667a622-2.png%3Fversion=1&modificationDate=1561213251717&cacheVersion=1&api=v2?version=1&modificationDate=1595588071467&cacheVersion=1&api=v2) | - -| | -| --- | -| ### **Detailed view of branches** | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/643203115/7fd7c5fa-9ad3-440f-9f5c-2a1a08f0fdb2.png%3Fversion=1&modificationDate=1561213277462&cacheVersion=1&api=v2?version=1&modificationDate=1595588072615&cacheVersion=1&api=v2) | - -| | -| --- | -| ### **Detailed view of pull requests** | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/643203115/6d436565-aabf-485d-a06d-9e7f09d4db80.png%3Fversion=1&modificationDate=1561213297453&cacheVersion=1&api=v2&width=818&height=457?version=1&modificationDate=1595588073102&cacheVersion=1&api=v2) | +### **Detailed view of commits** +![](https://bigbrassband.atlassian.net/wiki/download/attachments/643203115/5761be45-4320-4e87-a843-20936667a622-2.png%3Fversion=1&modificationDate=1561213251717&cacheVersion=1&api=v2?version=1&modificationDate=1595588071467&cacheVersion=1&api=v2) + +### **Detailed view of branches** +![](https://bigbrassband.atlassian.net/wiki/download/attachments/643203115/7fd7c5fa-9ad3-440f-9f5c-2a1a08f0fdb2.png%3Fversion=1&modificationDate=1561213277462&cacheVersion=1&api=v2?version=1&modificationDate=1595588072615&cacheVersion=1&api=v2) + +### **Detailed view of pull requests** +![](https://bigbrassband.atlassian.net/wiki/download/attachments/643203115/6d436565-aabf-485d-a06d-9e7f09d4db80.png%3Fversion=1&modificationDate=1561213297453&cacheVersion=1&api=v2&width=818&height=457?version=1&modificationDate=1595588073102&cacheVersion=1&api=v2) diff --git a/git-integration-for-jira-cloud/development-panel-locations-gij-cloud.md b/git-integration-for-jira-cloud/development-panel-locations-gij-cloud.md index ba76ee3..7ef2d50 100644 --- a/git-integration-for-jira-cloud/development-panel-locations-gij-cloud.md +++ b/git-integration-for-jira-cloud/development-panel-locations-gij-cloud.md @@ -17,4 +17,3 @@ In **Issue** and **Search** pages, the developer panel is visible on the rig On the Kanban board, click on an issue on the board grid. On a dialog that displays the selected Jira issue, click **Open Git integration** on the right sidebar. The Git integration panel is displayed. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923025834/gitcloud-kanban-devpanel-location.png?version=1&modificationDate=1635753982993&cacheVersion=1&api=v2&width=680&height=422) - diff --git a/git-integration-for-jira-cloud/development-status-in-jira-issue-searching-gij-cloud.md b/git-integration-for-jira-cloud/development-status-in-jira-issue-searching-gij-cloud.md index 1b28e03..10dfb07 100644 --- a/git-integration-for-jira-cloud/development-status-in-jira-issue-searching-gij-cloud.md +++ b/git-integration-for-jira-cloud/development-status-in-jira-issue-searching-gij-cloud.md @@ -20,4 +20,3 @@ This column is displayed in the following order of precedence: ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1940914287/image-20200724-103833.png?version=1&modificationDate=1631349148620&cacheVersion=1&api=v2) - diff --git a/git-integration-for-jira-cloud/edit-integration-gij-cloud.md b/git-integration-for-jira-cloud/edit-integration-gij-cloud.md index d7cee39..a38755f 100644 --- a/git-integration-for-jira-cloud/edit-integration-gij-cloud.md +++ b/git-integration-for-jira-cloud/edit-integration-gij-cloud.md @@ -6,7 +6,7 @@ taxonomy: category: git-integration-for-jira-cloud --- -On the Manage integrations page. click on ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Actions ➜ **Edit integration** for the selected integration to open its configuration page. +On the Manage integrations page. click on Actions ➜ **Edit integration** for the selected integration to open its configuration page. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923024559/gitcloud-manage-integration-actions-edit-cfg.png?version=1&modificationDate=1648985387880&cacheVersion=1&api=v2&width=680&height=271) @@ -20,14 +20,13 @@ The connection settings page contains configuration options to manage integratio Utilize the following options to configure the selected integration: -| | | -| --- | --- | | **Option** | **Description** | +| --- | --- | | _**Enable this integration**_ | Toggle to enable or disable this integration for use with Jira. | | _**Reconnect**_ | Click on this button to refresh the integration connection and indexing. | | _**Display Name**_ | This is the name that will appear on the Integration column in the Manage integrations page. | -| _Advanced:_
_**Custom API Path**_ | The Git Integration for Jira app supports this feature for GitHub and GitLab integrations. For more details, see [**Working with Custom API Path**](https://bigbrassband.com/custom-api-path-sel.html). | -| _Advanced:_
_**JMESPath Filters**_ | JMESPath is a query language for JSON used to filter API results and to limit which repositories are integrated. For more information, see [**Working with JMESPath Filters**](#). | +| _Advanced:_
_**Custom API Path**_ | The Git Integration for Jira app supports this feature for GitHub and GitLab integrations. For more details, see [**Working with Custom API Path**](/git-integration-for-jira-cloud/working-with-custom-api-path-gij-cloud). | +| _Advanced:_
_**JMESPath Filters**_ | JMESPath is a query language for JSON used to filter API results and to limit which repositories are integrated. For more information, see [**Working with JMESPath Filters**](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud). | ## Feature settings @@ -35,12 +34,11 @@ Utilize the following options to configure the selected integration: The Feature settings page contains configuration options related to user and project access, and the indexing triggers URL. -| | | -| --- | --- | | **Option** | **Description** | +| --- | --- | | _**Indexing triggers**_ | This is the automatically-generated webhook URL upon installation of Git Integration for Jira Cloud app.

Use the URL to setup webhook triggers to your git host service which allows immediate reindex of connected integrations. | -| _**Require User PAT**_ | Enable this option to require users to provide PAT which will be used for branch and merge/pull request creation/deletion (via the developer panel on the Jira issue page). This is a security feature of Git Integration for Jira app for git hosts that support two-factor authentication.

This option requires the [**Repository Browser**](/git-integration-for-jira-cloud/repository-browser-settings/) feature enabled.

This setting is only available for integrations connected via [**Git service integration** panel](/git-integration-for-jira-cloud/introduction-to-git-integration/). | -| _**Project permissions**_ | This feature allows administrators to configure project associations with repositories/integration to restrict which users can view development information. For more information, see [Associating project permissions](/git-integration-for-jira-cloud/associating-project-permissions-gij-cloud/). | +| _**Require User PAT**_ | Enable this option to require users to provide PAT which will be used for branch and merge/pull request creation/deletion (via the developer panel on the Jira issue page). This is a security feature of Git Integration for Jira app for git hosts that support two-factor authentication.

This option requires the [**Repository Browser**](/git-integration-for-jira-cloud/repository-browser-gij-cloud) feature enabled.

This setting is only available for integrations connected via [**Git service integration** panel](/git-integration-for-jira-cloud/introduction-to-git-integration-gij-cloud). | +| _**Project permissions**_ | This feature allows administrators to configure project associations with repositories/integration to restrict which users can view development information. For more information, see [Associating project permissions](/git-integration-for-jira-cloud/associating-project-permissions-gij-cloud). | ## Choose repositories diff --git a/git-integration-for-jira-cloud/edit-repository-gij-cloud.md b/git-integration-for-jira-cloud/edit-repository-gij-cloud.md index a87ac4e..11ece8e 100644 --- a/git-integration-for-jira-cloud/edit-repository-gij-cloud.md +++ b/git-integration-for-jira-cloud/edit-repository-gij-cloud.md @@ -8,7 +8,7 @@ taxonomy: --- HOSTED EXTERNAL -On the Manage repositories page, click ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Actions ➜ **Edit repository** for the selected repository to open its repository configuration page where you can change the settings of the connected repository. +On the Manage repositories page, click Actions ➜ **Edit repository** for the selected repository to open its repository configuration page where you can change the settings of the connected repository. ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1977384961/gitcloud-edit-repo-cfg-single-repo.png?version=1&modificationDate=1648989722770&cacheVersion=1&api=v2) @@ -16,9 +16,8 @@ Utilize the options below for configuring repository settings. ## Connection settings -| | | | -| --- | --- | --- | | **Option** | **Description** | **Repository type** | +| --- | --- | --- | | _**Enable this integration**_ | Toggle to enable/disable this repository for use with Jira. | SINGLE
INTEGRATION | | _**Display Name**_ | This is the alias that will appear in the Repository column. | SINGLE
INTEGRATION | | _**Repository Origin**_ | This is the URL path to a clone of the repository. | INTEGRATION | @@ -29,15 +28,14 @@ Utilize the options below for configuring repository settings. ## Feature settings -| | | | -| --- | --- | --- | | **Option** | **Description** | **Repository type** | +| --- | --- | --- | | _**Main Branch**_ | Set the main branch. The default setting is `master`. | SINGLE
INTEGRATION | | _**Indexing triggers**_ | Displays the indexing triggers URL for this repository. Click the adjacent copy icon to send the indexing triggers URL to the system clipboard. Use this URL to setup webhook to your git host service. | SINGLE
INTEGRATION | -| _**Tags**_ | Set whether to show all tags or show on tags with matching regex pattern. For more information on git tags, see [Git tags](/git-integration-for-jira-cloud/git-tags-gij-cloud/). | SINGLE
INTEGRATION | -| _**Smart Commits & Workflow Triggers**_ | Enable/disable this setting to allows the users to use the [smart commits](/git-integration-for-jira-cloud/smart-commits-gij-cloud/) feature. | SINGLE
INTEGRATION | -| _**Project Permissions: Restrict to projects**_ | The default setting is **Associate with all projects**. You can restrict access to the Repository Browser and Git Commit tabs (Advanced) for the selected repository by [setting the project associations](/git-integration-for-jira-cloud/associating-project-permissions-gij-cloud/). | SINGLE
INTEGRATION | -| _**Web Linking**_ | _Optional._

The web linking feature adds links to your git hosting provider directly into the Git Commits tab. For special integrations (Auto-Connect), this feature is configured automatically. For more information on about this topic, see [Web linking](/git-integration-for-jira-cloud/Web-linking). | SINGLE | +| _**Tags**_ | Set whether to show all tags or show on tags with matching regex pattern. For more information on git tags, see [Git tags](/git-integration-for-jira-cloud/git-tags-gij-cloud). | SINGLE
INTEGRATION | +| _**Smart Commits & Workflow Triggers**_ | Enable/disable this setting to allows the users to use the [smart commits](/git-integration-for-jira-cloud/smart-commits-gij-cloud) feature. | SINGLE
INTEGRATION | +| _**Project Permissions: Restrict to projects**_ | The default setting is **Associate with all projects**. You can restrict access to the Repository Browser and Git Commit tabs (Advanced) for the selected repository by [setting the project associations](/git-integration-for-jira-cloud/associating-project-permissions-gij-cloud). | SINGLE
INTEGRATION | +| _**Web Linking**_ | _Optional._

The web linking feature adds links to your git hosting provider directly into the Git Commits tab. For special integrations (Auto-Connect), this feature is configured automatically. For more information on about this topic, see [Web linking](/git-integration-for-jira-cloud/web-linking-gij-cloud). | SINGLE | Click **Save** to save the changes and apply the settings. diff --git a/git-integration-for-jira-cloud/email-notifications-from-atlassian-for-smart-commits-gij-cloud.md b/git-integration-for-jira-cloud/email-notifications-from-atlassian-for-smart-commits-gij-cloud.md index 19b68dd..6287fe5 100644 --- a/git-integration-for-jira-cloud/email-notifications-from-atlassian-for-smart-commits-gij-cloud.md +++ b/git-integration-for-jira-cloud/email-notifications-from-atlassian-for-smart-commits-gij-cloud.md @@ -29,35 +29,25 @@ For some example insights: ## Examples of Smart Commits Messages that Fail -| | -| --- | -| #### **1\. Smart commits without any value after the command** | -| For example, **JIRA-1** **#time** or **TES-1** **#comment** | -| ![smart commits error email notification example 1](https://bigbrassband.atlassian.net/wiki/download/attachments/805437441/sc-error01-example.png?version=1&modificationDate=1602060911583&cacheVersion=1&api=v2) | -| ![smart commits error email notification example 2](https://bigbrassband.atlassian.net/wiki/download/attachments/805437441/sc-error01-example2.png?version=1&modificationDate=1602061171866&cacheVersion=1&api=v2) | - -| | -| --- | -| #### **2\. Smart commits with an invalid issue-key** | -| For example, **JIRA-700000** **#time** **4h 30m** | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/805437441/sc-error02-example.png?version=1&modificationDate=1602061437954&cacheVersion=1&api=v2) | - -| | -| --- | -| #### **3\. Smart commits with a non-editable workflow state** | -| Example: | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/805437441/bitbucket-non-editable-workflow-state.png?version=1&modificationDate=1602061633086&cacheVersion=1&api=v2) | +#### **1\. Smart commits without any value after the command** +For example, **JIRA-1** **#time** or **TES-1** **#comment** +![smart commits error email notification example 1](https://bigbrassband.atlassian.net/wiki/download/attachments/805437441/sc-error01-example.png?version=1&modificationDate=1602060911583&cacheVersion=1&api=v2) +![smart commits error email notification example 2](https://bigbrassband.atlassian.net/wiki/download/attachments/805437441/sc-error01-example2.png?version=1&modificationDate=1602061171866&cacheVersion=1&api=v2) + +#### **2\. Smart commits with an invalid issue-key** +For example, **JIRA-700000** **#time** **4h 30m** +![](https://bigbrassband.atlassian.net/wiki/download/attachments/805437441/sc-error02-example.png?version=1&modificationDate=1602061437954&cacheVersion=1&api=v2) + +#### **3\. Smart commits with a non-editable workflow state** +Example: +![](https://bigbrassband.atlassian.net/wiki/download/attachments/805437441/bitbucket-non-editable-workflow-state.png?version=1&modificationDate=1602061633086&cacheVersion=1&api=v2) ## Examples of Smart Commits Messages that are Processed Correctly -| | -| --- | -| #### **1\. Smart commits with a command and a value for it** | -| Example:
**JIRA-1** **#time** **1w 2d 4h 30m** | -| _The above example adds the time of 1 week, 2 days, 4 hours and 30 minutes (220.5 hours) to the Jira issue._ | - -| | -| --- | -| #### **2\. Smart commits with a correct transition name** | -| Example:
**JIRA-1** **#close** | -| _The above example will move the stage of the Jira issue as_ CLOSED. | \ No newline at end of file +#### **1\. Smart commits with a command and a value for it** +Example:
**JIRA-1** **#time** **1w 2d 4h 30m** +_The above example adds the time of 1 week, 2 days, 4 hours and 30 minutes (220.5 hours) to the Jira issue._ + +#### **2\. Smart commits with a correct transition name** +Example:
**JIRA-1** **#close** +_The above example will move the stage of the Jira issue as_ CLOSED. \ No newline at end of file diff --git a/git-integration-for-jira-cloud/empty-list-of-repositories-after-integration-of-azure-repos-gij-cloud.md b/git-integration-for-jira-cloud/empty-list-of-repositories-after-integration-of-azure-repos-gij-cloud.md index e043698..bae9e85 100644 --- a/git-integration-for-jira-cloud/empty-list-of-repositories-after-integration-of-azure-repos-gij-cloud.md +++ b/git-integration-for-jira-cloud/empty-list-of-repositories-after-integration-of-azure-repos-gij-cloud.md @@ -12,7 +12,7 @@ After integrating Azure DevOps to Jira, the Tracked Folder/Repositories dialog d ## Diagnosis -The integration status is UPDATED but users will see a blank list when performing ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Actions**> **Show integration repositories** in the Git Integration app manage repository configuration list. +The integration status is UPDATED but users will see a blank list when performing **Actions**> **Show integration repositories** in the Git Integration app manage repository configuration list. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/421298248/azure-no-repo-view-repos-cloud.png?version=1&modificationDate=1586356225011&cacheVersion=1&api=v2&width=557&height=345) @@ -24,9 +24,9 @@ If the problem still persists: 1. Follow the solutions outlined in the following articles: - 1. [OAuth connection error or error 401 page with Azure DevOps integration](/git-integration-for-jira-cloud/oauth-connection-error-or-error-401-page-with-azure-devops-integration/) + 1. [OAuth connection error or error 401 page with Azure DevOps integration](/git-integration-for-jira-cloud/oauth-connection-error-or-error-401-page-with-azure-devops-integration-gij-cloud) - 2. [OAuth connection error or error 401 page with Azure DevOps with Active Directory integration](/git-integration-for-jira-cloud/oauth-connection-error-or-error-401-page-with-azure-devops-with-active-directory-integration/) + 2. [OAuth connection error or error 401 page with Azure DevOps with Active Directory integration](/git-integration-for-jira-cloud/oauth-connection-error-or-error-401-page-with-azure-devops-with-active-directory-integration-gij-cloud) -2. Configure [Creating Personal Access Tokens](/git-integration-for-jira-cloud/creating-personal-access-tokens/)). +2. Configure [Creating Personal Access Tokens](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud). diff --git a/git-integration-for-jira-cloud/enable-beta-features-setting-gij-cloud.md b/git-integration-for-jira-cloud/enable-beta-features-setting-gij-cloud.md index ddb7560..27e2c93 100644 --- a/git-integration-for-jira-cloud/enable-beta-features-setting-gij-cloud.md +++ b/git-integration-for-jira-cloud/enable-beta-features-setting-gij-cloud.md @@ -7,7 +7,7 @@ taxonomy: --- -This setting is part of the [**General settings**](https://bigbrassband.atlassian.net/wiki/spaces/GITCLOUD/pages/781942911) configuration page for Git Integration for Jira Cloud. +This setting is part of the [**General settings**](/git-integration-for-jira-cloud/general-settings-gij-cloud) configuration page for Git Integration for Jira Cloud. **Default settings** This setting is disabled in [**Git Integration for Jira Cloud**](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?tab=overview&hosting=cloud) app by default. diff --git a/git-integration-for-jira-cloud/enable-git-integration-app-smart-commits-setting-gij-cloud.md b/git-integration-for-jira-cloud/enable-git-integration-app-smart-commits-setting-gij-cloud.md index 0835d8c..cd07c2f 100644 --- a/git-integration-for-jira-cloud/enable-git-integration-app-smart-commits-setting-gij-cloud.md +++ b/git-integration-for-jira-cloud/enable-git-integration-app-smart-commits-setting-gij-cloud.md @@ -8,13 +8,13 @@ taxonomy: --- -These settings are part of the [General settings](/git-integration-for-jira-cloud/General-Settings) configuration page for Git Integration for Jira Cloud under [Jira Development Information settings](/git-integration-for-jira-cloud/jira-development-information-settings/). +These settings are part of the [General settings](/git-integration-for-jira-cloud/general-settings-gij-cloud) configuration page for Git Integration for Jira Cloud under [Jira Development Information settings](/git-integration-for-jira-cloud/jira-development-information-settings-gij-cloud). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1207829205/gitcloud-gencfg-enable-app-smart-commits.png?version=1&modificationDate=1645098328920&cacheVersion=1&api=v2&width=548&height=253) -This setting engages BigBrassBand's Git Integration Smart Commit processing for `#time`, `#comment`, `#transitions` and `#label`. For more information, see our [Smart Commits documentation^](/git-integration-for-jira-cloud/smart-commits/). +This setting engages BigBrassBand's Git Integration Smart Commit processing for `#time`, `#comment`, `#transitions` and `#label`. For more information, see our [Smart Commits documentation^](/git-integration-for-jira-cloud/smart-commits-gij-cloud). -Turning this setting to `ON` automatically disables the [**Send Development Information to Jira Cloud**](/git-integration-for-jira-cloud/send-development-information-to-jira-cloud-setting/) and [**Enable Jira Cloud Smart Commits & Workflow Triggers**](/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-setting/) settings. +Turning this setting to `ON` automatically disables the [**Send Development Information to Jira Cloud**](/git-integration-for-jira-cloud/send-development-information-to-jira-cloud-setting-gij-cloud) and [**Enable Jira Cloud Smart Commits & Workflow Triggers**](/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-setting-gij-cloud) settings. After all the settings have been configured according to your requirements, click **Update** to apply the changes. diff --git a/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-gij-cloud.md b/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-gij-cloud.md index 0a651bd..0595373 100644 --- a/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-gij-cloud.md +++ b/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-gij-cloud.md @@ -6,9 +6,9 @@ taxonomy: category: git-integration-for-jira-cloud --- -This setting engages the native Jira Cloud Smart Commit processing (only `#time`, `#comment`, and `#transitions`) as well as enables [Automatic Workflow Triggers](git-integration-for-jira-cloud/automatic-workflow-triggers/). +This setting engages the native Jira Cloud Smart Commit processing (only `#time`, `#comment`, and `#transitions`) as well as enables [Automatic Workflow Triggers](/git-integration-for-jira-cloud/automatic-workflow-triggers-gij-cloud). For more information - see Atlassian's [Smart Commits^](https://confluence.atlassian.com/adminjiracloud/enable-smart-commits-776830276.html) or [Automatic Workflow Triggers^](https://confluence.atlassian.com/adminjiracloud/configuring-workflow-triggers-776636696.html) documentation. -For detailed information on this setting, see [General settings: Enable Jira Cloud smart commits, Automation for Jira and workflow triggers](/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-setting/). +For detailed information on this setting, see [General settings: Enable Jira Cloud smart commits, Automation for Jira and workflow triggers](/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-setting-gij-cloud). diff --git a/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-setting-gij-cloud.md b/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-setting-gij-cloud.md index 6fc5882..9589972 100644 --- a/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-setting-gij-cloud.md +++ b/git-integration-for-jira-cloud/enable-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-setting-gij-cloud.md @@ -8,14 +8,14 @@ taxonomy: --- -These settings are part of the [General settings](/git-integration-for-jira-cloud/General-Settings) configuration page for Git Integration for Jira Cloud under [Jira Development Information settings](/git-integration-for-jira-cloud/jira-development-information-settings/). +These settings are part of the [General settings](/git-integration-for-jira-cloud/general-settings-gij-cloud) configuration page for Git Integration for Jira Cloud under [Jira Development Information settings](/git-integration-for-jira-cloud/jira-development-information-settings-gij-cloud). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1207796196/gitcloud-gencfg-enable-smart-commits-automation.png?version=1&modificationDate=1645098206103&cacheVersion=1&api=v2&width=548&height=253) -This setting engages the native Jira Cloud Smart Commit processing. At this time only `#time`, `#comment` and `#transitions` are supported for the triggers. This also enables the [Automatic Workflow Triggers](/git-integration-for-jira-cloud/automatic-workflow-triggers/) feature. +This setting engages the native Jira Cloud Smart Commit processing. At this time only `#time`, `#comment` and `#transitions` are supported for the triggers. This also enables the [Automatic Workflow Triggers](/git-integration-for-jira-cloud/automatic-workflow-triggers-gij-cloud) feature. The automatic workflow triggers allows you to use your development activity to make automatic changes in your Jira project workflows. For example, you can use the workflow trigger to transition your Jira issues. -For more information on Automation for Jira, see article [Git Integration + Jira Automation](/git-integration-for-jira-cloud/git-integration-jira-automation/). +For more information on Automation for Jira, see article [Git Integration + Jira Automation](/git-integration-for-jira-cloud/git-integration-jira-automation-gij-cloud). After all the settings have been configured according to your requirements, click **Update** to apply the changes. diff --git a/git-integration-for-jira-cloud/error-while-reindexing-java-heap-space-object-too-large-rejecting-the-pack-gij-cloud.md b/git-integration-for-jira-cloud/error-while-reindexing-java-heap-space-object-too-large-rejecting-the-pack-gij-cloud.md index 979c0ac..02b1b5e 100644 --- a/git-integration-for-jira-cloud/error-while-reindexing-java-heap-space-object-too-large-rejecting-the-pack-gij-cloud.md +++ b/git-integration-for-jira-cloud/error-while-reindexing-java-heap-space-object-too-large-rejecting-the-pack-gij-cloud.md @@ -14,9 +14,8 @@ The Git Integration for Jira application uses the [JGit](https://www.eclipse.or Jira admins will see a message similar to the one below in the Jira `/application-logs/atlassian-jira.log:` -| | -| --- | | **Error** | +| --- | | ```java
Сan't auto-deploy a new repository https://server/project/repository.git
com.bigbrassband.jira.git.exceptions.InvalidRemoteOperationException: Specified origin https://server/project/repository.git is incorrect or not supported
at com.bigbrassband.jira.git.services.gitmanager.MultipleGitRepositoryManagerImpl.setupRepository(MultipleGitRepositoryManagerImpl.java:800)
at com.bigbrassband.jira.git.services.gitmanager.MultipleGitRepositoryManagerImpl.deployRepository(MultipleGitRepositoryManagerImpl.java:868)
at com.bigbrassband.jira.git.services.async.DoSynchronizationOfAggregatedRepoTask.createNewRepository(DoSynchronizationOfAggregatedRepoTask.java:156)
at com.bigbrassband.jira.git.services.async.DoSynchronizationOfAggregatedRepoTask.run(DoSynchronizationOfAggregatedRepoTask.java:117)
at com.bigbrassband.jira.git.services.async.BigReindexTask.synchronize(BigReindexTask.java:185)
at com.bigbrassband.jira.git.services.async.BigReindexTask.run(BigReindexTask.java:95)
at com.bigbrassband.jira.git.services.async.AsyncProcessorImpl$AsyncTaskWrapper.run(AsyncProcessorImpl.java:110)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.eclipse.jgit.api.errors.TransportException: Object too large (2,271,263,009 bytes), rejecting the pack. Max object size limit is 2,147,483,639 bytes.
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:254)
at org.eclipse.jgit.api.CloneCommand.fetch(CloneCommand.java:306)
at org.eclipse.jgit.api.CloneCommand.call(CloneCommand.java:200)
at com.bigbrassband.jira.git.services.gitmanager.MultipleGitRepositoryManagerImpl.runCloneCommand(MultipleGitRepositoryManagerImpl.java:693)
at com.bigbrassband.jira.git.services.gitmanager.MultipleGitRepositoryManagerImpl.setupRepository(MultipleGitRepositoryManagerImpl.java:789)
... 11 more
``` | ## Solutions @@ -35,7 +34,7 @@ Making any change to a git repository's history can result in loss of data. Proc * Move large files to [GitLFS](https://git-lfs.github.com/) which is supported by the Git Integration for Jira app. -* Filter out the repository from the special integrations (GitHub, GitLab, AWS CodeCommit, Microsoft TFS/Azure DevOps/VSTS, etc) using [Custom API Path](https://bigbrassband.atlassian.net/wiki/spaces/BBBSUPPORT/pages/133267463) or [JMESPath Filters](https://bigbrassband.atlassian.net/wiki/spaces/BBBSUPPORT/pages/133234739/Working+with+JMESPath+Filters). +* Filter out the repository from the special integrations (GitHub, GitLab, AWS CodeCommit, Microsoft TFS/Azure DevOps/VSTS, etc) using [Custom API Path](/git-integration-for-jira-cloud/working-with-custom-api-path-gij-cloud) or [JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud). **Contact Us** diff --git a/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud.md b/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud.md index 4dc125a..7c53dbf 100644 --- a/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud.md +++ b/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud.md @@ -10,9 +10,8 @@ See also [Feature Comparison](https://bigbrassband.atlassian.net/wiki/spaces/GIT The [Git Integration for Jira Cloud](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=overview) app offers a variety of integration options and features. The below matrix explains which features are offered when using a specific type of integration. For any questions, contact [BigBrassBand Support](https://bigbrassband.atlassian.net/servicedesk/customer/portals/). -| | | | | -| --- | --- | --- | --- | | | **Git service integrations**

\[Classic full feature integrations\] | **Single git repository integrations**

\[Limited feature connect\] | **Webhook indexing integrations**

\[Limited feature connect\] | +| --- | --- | --- | --- | | **Works with git servers behind firewall** | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | **View commits, branches, pull/merge requests in Jira** | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Commits and branches

![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Pull/merge requests | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | **Pull / Merge Request Reviewers and Approvals Shown in Jira** | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Pull/merge requests | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) GitHub

![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Azure DevOps, VSTS, TFS

![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) GitLab | @@ -36,10 +35,10 @@ The [Git Integration for Jira Cloud](https://marketplace.atlassian.com/apps/4984 For more information about the different types of integrations: -[Classic Indexing Explainer](/git-integration-for-jira-cloud/classic-indexing-explainer/) +[Classic Indexing Explainer](/git-integration-for-jira-cloud/classic-indexing-explainer-gij-cloud) -[Webhook Indexing Explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer/) +[Webhook Indexing Explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer-gij-cloud) -[Setting up integrations](/git-integration-for-jira-cloud/setting-up-integrations/) +[Setting up integrations](/git-integration-for-jira-cloud/setting-up-integrations-gij-cloud) If you have questions or need additional support - contact [BigBrassBand Support](https://bigbrassband.atlassian.net/servicedesk/customer/portals/). \ No newline at end of file diff --git a/git-integration-for-jira-cloud/features-gij-cloud.md b/git-integration-for-jira-cloud/features-gij-cloud.md index a9819e2..fdba00c 100644 --- a/git-integration-for-jira-cloud/features-gij-cloud.md +++ b/git-integration-for-jira-cloud/features-gij-cloud.md @@ -8,32 +8,32 @@ taxonomy: --- On this page you will find topics related to the supported features of the app. -* [Git Roll Up Issue Tab](/git-integration-for-jira-cloud/git-roll-up-issue-tab/) (Git Integration for Jira Cloud) +* [Git Roll Up Issue Tab](/git-integration-for-jira-cloud/git-roll-up-issue-tab-gij-cloud) (Git Integration for Jira Cloud) -* [Git Commits Issue Tab and Project Pages](/wiki/spaces/GITCLOUD/pages/138346498/Git+Commits+Issue+Tab+and+Project+Pages) (Git Integration for Jira Cloud) +* [Git Commits Issue Tab and Project Pages](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-pages-gij-cloud) (Git Integration for Jira Cloud) -* [Issue Git Source Code Panel](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-pages/) (Git Integration for Jira Cloud) +* [Issue Git Source Code Panel](/git-integration-for-jira-cloud/issue-git-source-code-panel-gij-cloud) (Git Integration for Jira Cloud) -* [Repository Browser: Viewing all repositories](/git-integration-for-jira-cloud/repository-browser-viewing-all-repositories/) (Git Integration for Jira Cloud) +* [Repository Browser: Viewing all repositories](/git-integration-for-jira-cloud/repository-browser-viewing-all-repositories-gij-cloud) (Git Integration for Jira Cloud) -* [Jira Development Information](/git-integration-for-jira-cloud/jira-development-information/) (Git Integration for Jira Cloud) +* [Jira Development Information](/git-integration-for-jira-cloud/jira-development-information-gij-cloud) (Git Integration for Jira Cloud) -* [Classic Indexing Explainer](/git-integration-for-jira-cloud/classic-indexing-explainer/) (Git Integration for Jira Cloud) +* [Classic Indexing Explainer](/git-integration-for-jira-cloud/classic-indexing-explainer-gij-cloud) (Git Integration for Jira Cloud) -* [Git Integration Server/Data Center vs Jira Cloud - Feature Comparison](/git-integration-server-data-center-vs-jira-cloud-feature-comparison/) (Git Integration for Jira Cloud) +* [Git Integration Server/Data Center vs Jira Cloud - Feature Comparison](/git-integration-for-jira-cloud/git-integration-server-data-center-vs-jira-cloud-feature-comparison-gij-cloud) (Git Integration for Jira Cloud) -* [Migrating from Jira Server + Data Center to Jira Cloud](/git-integration-for-jira-cloud/migrating-from-jira-server-data-center-to-jira-cloud/) (Git Integration for Jira Cloud) +* [Migrating from Jira Server + Data Center to Jira Cloud](/git-integration-for-jira-cloud/migrating-from-jira-server-data-center-to-jira-cloud-gij-cloud) (Git Integration for Jira Cloud) -* [Create branch](/git-integration-for-jira-cloud/Create-branch) (Git Integration for Jira Cloud) +* [Create branch](/git-integration-for-jira-cloud/create-branch-gij-cloud) (Git Integration for Jira Cloud) -* [Create pull or merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request/) (Git Integration for Jira Cloud) +* [Create pull or merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud) (Git Integration for Jira Cloud) -* [General Settings](/git-integration-for-jira-cloud/General-Settings) (Git Integration for Jira Cloud) +* [General Settings](/git-integration-for-jira-cloud/general-settings-gij-cloud) (Git Integration for Jira Cloud) -* [User Settings](/git-integration-for-jira-cloud/User-Settings) (Git Integration for Jira Cloud) +* [User Settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) (Git Integration for Jira Cloud) -* [Webhook Indexing Explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer/) (Git Integration for Jira Cloud) +* [Webhook Indexing Explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer-gij-cloud) (Git Integration for Jira Cloud) -* [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud/) (Git Integration for Jira Cloud) +* [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud) (Git Integration for Jira Cloud) -* [Git Integration + Jira Automation](/git-integration-for-jira-cloud/git-integration-jira-automation/) (Git Integration for Jira Cloud) \ No newline at end of file +* [Git Integration + Jira Automation](/git-integration-for-jira-cloud/git-integration-jira-automation-gij-cloud) (Git Integration for Jira Cloud) \ No newline at end of file diff --git a/git-integration-for-jira-cloud/general-gij-cloud.md b/git-integration-for-jira-cloud/general-gij-cloud.md index ab92adf..093f077 100644 --- a/git-integration-for-jira-cloud/general-gij-cloud.md +++ b/git-integration-for-jira-cloud/general-gij-cloud.md @@ -66,4 +66,4 @@ We test this on huge Git repositories in large Jira instances. Over 5000 organ For a more comprehensive view, see **[Git Integration for Jira app Version History »](https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/versions "Git add-on Version History")**. -In the Version History page, you can try or buy the Git Integration for Jira Cloud app or download it for use with **[manual installation »](https://bigbrassband.com/git-integration-for-jira/documentation/installation.html#gitctrlvwr_inst_manual "Git add-on Manual Installation")**. \ No newline at end of file +In the Version History page, you can try or buy the Git Integration for Jira Cloud app or download it for use with **[manual installation »](/git-integration-for-jira-cloud/installation-and-setup-gij-cloud "Git add-on Manual Installation")**. \ No newline at end of file diff --git a/git-integration-for-jira-cloud/general-settings-for-administrators-gij-cloud.md b/git-integration-for-jira-cloud/general-settings-for-administrators-gij-cloud.md index 6f7a924..bb5726e 100644 --- a/git-integration-for-jira-cloud/general-settings-for-administrators-gij-cloud.md +++ b/git-integration-for-jira-cloud/general-settings-for-administrators-gij-cloud.md @@ -14,15 +14,18 @@ The Git Integration for Jira app introduces the General settings page which cont Open the **General settings** page in the Jira Apps Management (**Applications** _page in Jira 7 and up_) to enable/disable features of the Git Integration for Jira Server/Data Center app. -| | | -| --- | --- | -| The **General settings** configuration page can be accessed thru the following locations: | | -| * Jira dashboard ➜ Apps menu ➜ Git Integration: Manage Git repositories ➜ Git Integration for Jira (sidebar) ➜ **General settings**. | * Jira dashboard ➜ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Jira settings ➜ Apps ➜ **General settings** (sidebar). | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923025087/gitcloud-gitmenu-apps-gencfg-sel.png?version=2&modificationDate=1638618666472&cacheVersion=1&api=v2) | ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923025087/gitcloud-gencfg-admin-apps-menu.png?version=2&modificationDate=1638619051443&cacheVersion=1&api=v2) | +The **General settings** configuration page can be accessed thru the following locations: +* Jira dashboard ➜ Apps menu ➜ Git Integration: Manage Git repositories ➜ Git Integration for Jira (sidebar) ➜ **General settings**. -If you're using Jira Server or Jira Data Center, [view this page instead](/wiki/spaces/GITSERVER/pages/966885431/General+Settings). +![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923025087/gitcloud-gitmenu-apps-gencfg-sel.png?version=2&modificationDate=1638618666472&cacheVersion=1&api=v2) + +* Jira dashboard ➜Jira settings ➜ Apps ➜ **General settings** (sidebar). + +![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923025087/gitcloud-gencfg-admin-apps-menu.png?version=2&modificationDate=1638619051443&cacheVersion=1&api=v2) + +If you're using Jira Server or Jira Data Center, [view this page instead](/git-integration-for-jira-self-managed/general-gij-self-managed). After making changes to the configuration settings, click **Save** to apply the changes. -For detailed information about this feature and the supported settings, see [Administration: General settings](/git-integration-for-jira-cloud/General-Settings). +For detailed information about this feature and the supported settings, see [Administration: General settings](/git-integration-for-jira-cloud/general-settings-gij-cloud). diff --git a/git-integration-for-jira-cloud/general-settings-gij-cloud.md b/git-integration-for-jira-cloud/general-settings-gij-cloud.md index a490fe3..dc400f4 100644 --- a/git-integration-for-jira-cloud/general-settings-gij-cloud.md +++ b/git-integration-for-jira-cloud/general-settings-gij-cloud.md @@ -14,31 +14,33 @@ The Git Integration for Jira Cloud app General settings page allows administrato Open the **General settings** page in the Jira Apps Management (**Applications** _page in Jira 7 and up_) to enable/disable features of the Git Integration for Cloud app. -| | | -| --- | --- | -| The **General settings** configuration page can be accessed thru the following location: | | -| * Jira dashboard **Git** menu ➜ Apps ➜ Git Integration: Manage Git repositories ➜ **General settings**. | * Jira dashboard ➜ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Jira settings ➜ Apps ➜ **General settings** (sidebar). | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/781942911/gitcloud-gitmenu-apps-gencfg-sel.png?version=1&modificationDate=1633776362871&cacheVersion=1&api=v2) | ![](https://bigbrassband.atlassian.net/wiki/download/attachments/781942911/gitcloud-gencfg-admin-apps-menu.png?version=1&modificationDate=1633776790816&cacheVersion=1&api=v2) | +The **General settings** configuration page can be accessed thru the following location: +* Jira dashboard **Git** menu ➜ Apps ➜ Git Integration: Manage Git repositories ➜ **General settings**. +![](https://bigbrassband.atlassian.net/wiki/download/attachments/781942911/gitcloud-gitmenu-apps-gencfg-sel.png?version=1&modificationDate=1633776362871&cacheVersion=1&api=v2) + +* Jira dashboard ➜Jira settings ➜ Apps ➜ **General settings** (sidebar). +![](https://bigbrassband.atlassian.net/wiki/download/attachments/781942911/gitcloud-gencfg-admin-apps-menu.png?version=1&modificationDate=1633776790816&cacheVersion=1&api=v2) + ## Settings index -* [Git roll up issue tab setting](/git-integration-for-jira-cloud/git-roll-up-issue-tab-setting/) (Git Integration for Jira Cloud) +* [Git roll up issue tab setting](/git-integration-for-jira-cloud/git-roll-up-issue-tab-setting-gij-cloud) (Git Integration for Jira Cloud) -* [Git commits issue tab and project page](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page/) (Git Integration for Jira Cloud) +* [Git commits issue tab and project page](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page-gij-cloud) (Git Integration for Jira Cloud) -* [Issue git source code panel setting](/git-integration-for-jira-cloud/issue-git-source-code-panel-setting/) (Git Integration for Jira Cloud) +* [Issue git source code panel setting](/git-integration-for-jira-cloud/issue-git-source-code-panel-setting-gij-cloud) (Git Integration for Jira Cloud) -* [Repository browser settings](/git-integration-for-jira-cloud/repository-browser-settings/) (Git Integration for Jira Cloud) +* [Repository browser settings](/git-integration-for-jira-cloud/repository-browser-settings-gij-cloud) (Git Integration for Jira Cloud) -* [Git integration options](git-integration-for-jira-cloud/git-integration-options/) (Git Integration for Jira Cloud) +* [Git integration options](/git-integration-for-jira-cloud/git-integration-options-gij-cloud) (Git Integration for Jira Cloud) -* [Jira development information settings](/git-integration-for-jira-cloud/jira-development-information-settings/) (Git Integration for Jira Cloud) +* [Jira development information settings](/git-integration-for-jira-cloud/jira-development-information-settings-gij-cloud) (Git Integration for Jira Cloud) -* [General settings for administrators](/git-integration-for-jira-cloud/general-settings-for-administrators/) (Git Integration for Jira Cloud) +* [General settings for administrators](/git-integration-for-jira-cloud/general-settings-for-administrators-gij-cloud) (Git Integration for Jira Cloud) -* [GitKraken integration settings](/git-integration-for-jira-cloud/gitkraken-integration-settings/) (Git Integration for Jira Cloud) +* [GitKraken integration settings](/git-integration-for-jira-cloud/gitkraken-integration-settings-gij-cloud) (Git Integration for Jira Cloud) -* [Enable beta features setting](/git-integration-for-jira-cloud/enable-beta-features-setting/) (Git Integration for Jira Cloud) +* [Enable beta features setting](/git-integration-for-jira-cloud/enable-beta-features-setting-gij-cloud) (Git Integration for Jira Cloud) diff --git a/git-integration-for-jira-cloud/generating-ssh-keys-gij-cloud.md b/git-integration-for-jira-cloud/generating-ssh-keys-gij-cloud.md index 49a32b6..8f1c7fe 100644 --- a/git-integration-for-jira-cloud/generating-ssh-keys-gij-cloud.md +++ b/git-integration-for-jira-cloud/generating-ssh-keys-gij-cloud.md @@ -8,9 +8,8 @@ taxonomy: --- Configure and generate SSH keys for the following git hosting systems by following the reference links on each sub-section: -| | -| --- | | **Beanstalk** | +| --- | | * For MacOS, see [Working with Git on MacOS](http://guides.beanstalkapp.com/version-control/git-on-mac.html).

* For Windows, see [Working with Git on Windows](http://guides.beanstalkapp.com/version-control/git-on-windows.html).

* For Linux, see [Working with Git on Linux](http://guides.beanstalkapp.com/version-control/git-on-linux.html). | | **Bitbucket** | | * For MacOS/Linux, see [Setting up SSH for Git on MacOS/Linux](https://support.atlassian.com/bitbucket-cloud/docs/set-up-an-ssh-key/#Set-up-SSH-on-macOS-Linux).

* For Windows, see [Set up SSH for Git on Windows](https://support.atlassian.com/bitbucket-cloud/docs/set-up-an-ssh-key/). | @@ -23,7 +22,7 @@ Configure and generate SSH keys for the following git hosting systems by followi | **GitLab** | | * See reference, [Installing Git for MacOS/Windows/Linux](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git).

* For creating SSH keys, see [Generating SSH Public Key](https://docs.gitlab.com/ee/ssh/index.html). Also see the video demonstration [here](https://about.gitlab.com/blog/2014/03/04/add-ssh-key-screencast/). | | **GitLab CE/EE** | -| ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Follow the above GitLab references for GitLab CE/EE. Then verify that your GitLab server should have the following SSH settings:

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923023647/gitlab-server-ssh-settings(c).png?version=1&modificationDate=1630063569186&cacheVersion=1&api=v2&width=680&height=471)

* Enabled Git access protocols -- **Both SSH and HTTP(s)**

* RSA SSH keys -- **Are allowed**


Other SSH key formats may be supported by Git Integration for Jira app, but prefer to use RSA format for your SSH git connections. | +|Follow the above GitLab references for GitLab CE/EE. Then verify that your GitLab server should have the following SSH settings:

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923023647/gitlab-server-ssh-settings(c).png?version=1&modificationDate=1630063569186&cacheVersion=1&api=v2&width=680&height=471)

* Enabled Git access protocols -- **Both SSH and HTTP(s)**

* RSA SSH keys -- **Are allowed**


Other SSH key formats may be supported by Git Integration for Jira app, but prefer to use RSA format for your SSH git connections. | | **Git-scm** | | * See reference, [Installing Git for MacOS/Windows/Linux](https://git-scm.com/book/en/Getting-Started-Installing-Git).

* For creating SSH keys, see [Connecting to GitHub with SSH](https://help.github.com/en/articles/connecting-to-github-with-ssh). | | **Gitolite** | diff --git a/git-integration-for-jira-cloud/gerrit-end-of-life-gij-cloud.md b/git-integration-for-jira-cloud/gerrit-end-of-life-gij-cloud.md index 02ae3dc..159444f 100644 --- a/git-integration-for-jira-cloud/gerrit-end-of-life-gij-cloud.md +++ b/git-integration-for-jira-cloud/gerrit-end-of-life-gij-cloud.md @@ -10,4 +10,4 @@ The Gerrit open-source community actively supports the last 2 releases on a best For more information, see [Gerrit support page](https://www.gerritcodereview.com/support.html). -End of life for old release happens implicitly when a new Gerrit version is released, and is announced via the [project news](https://www.gerritcodereview.com/news.html). \ No newline at end of file +End of life for old release happens implicitly when a new Gerrit version is released, and is announced via the [project news](https://www.gerritcodereview.com/news.html). diff --git a/git-integration-for-jira-cloud/gerrit-gij-cloud.md b/git-integration-for-jira-cloud/gerrit-gij-cloud.md index f88f383..f431319 100644 --- a/git-integration-for-jira-cloud/gerrit-gij-cloud.md +++ b/git-integration-for-jira-cloud/gerrit-gij-cloud.md @@ -6,7 +6,7 @@ taxonomy: category: git-integration-for-jira-cloud --- -Using **Jira Server or Data Center**? [See the corresponding article](/git-integration-for-jira-self-managed/gerrit/). +Using **Jira Server or Data Center**? [See the corresponding article](/git-integration-for-jira-self-managed/gerrit-gij-self-managed). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/86474926/gerrit-banner-logo.png?version=1&modificationDate=1590827774620&cacheVersion=1&api=v2&width=272&height=112) @@ -83,7 +83,7 @@ BigBrassBand recommends to use the Full feature integration for Gerrit. 4. Click **View full commit** to view the code diff. -For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues/). +For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues-gij-cloud). ## Default branch diff --git a/git-integration-for-jira-cloud/gerrit-webhook-indexing-integration-gij-cloud.md b/git-integration-for-jira-cloud/gerrit-webhook-indexing-integration-gij-cloud.md index 069d569..422cbf2 100644 --- a/git-integration-for-jira-cloud/gerrit-webhook-indexing-integration-gij-cloud.md +++ b/git-integration-for-jira-cloud/gerrit-webhook-indexing-integration-gij-cloud.md @@ -12,4 +12,5 @@ COMING SOON COMING SOON COMING SOON COMING SOON ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **UNDER CONSTRUCTION** ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) -![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) \ No newline at end of file +![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) + diff --git a/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page-gij-cloud.md b/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page-gij-cloud.md index 3336b44..a43e30c 100644 --- a/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page-gij-cloud.md @@ -8,7 +8,7 @@ taxonomy: --- -This setting is part of the [**General settings**](/git-integration-for-jira-cloud/General-Settings) configuration page for Git Integration for Jira Cloud. +This setting is part of the [**General settings**](/git-integration-for-jira-cloud/general-settings-gij-cloud) configuration page for Git Integration for Jira Cloud. **Default settings** This setting is enabled in [**Git Integration for Jira Cloud**](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?tab=overview&hosting=cloud) app by default. @@ -20,7 +20,7 @@ This setting is turned off by default in [**Dev Info for Jira Cloud**](https:// This setting will enable/disable the **Git Commits Issue tab** and the **Git Commits Project** page. These locations show the list of git commits associated to the Jira Issue and Jira Project, respectively. The list is grouped by repository and sorted by commit time. -For more details, see [**Features: Git Commits Issue tab and Project Page (Jira Cloud)**](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page/). +For more details, see [**Features: Git Commits Issue tab and Project Page (Jira Cloud)**](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page-gij-cloud). **Permissions** The **View developer tools** _permission_ is required to view the Git Commits Issue Tab and Projects Page. Jira users must also have the **Browse Project** _permissions_ to a project associated with a repository to view. diff --git a/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-pages-gij-cloud.md b/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-pages-gij-cloud.md index 52c4f3a..f4ae234 100644 --- a/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-pages-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-pages-gij-cloud.md @@ -11,7 +11,7 @@ taxonomy: **Features** * By default, [Git Integration for Jira](https://marketplace.atlassian.com/4984) has the Git Commits Issue and Project Tabs enabled. ([How to disable](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page/)) -* By default, [Dev Info for Jira](https://marketplace.atlassian.com/1219270) has the Git Commits Issue and Project Tabs disabled. ([How to enable](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page/)) +* By default, [Dev Info for Jira](https://marketplace.atlassian.com/1219270) has the Git Commits Issue and Project Tabs disabled. ([How to enable](/git-integration-for-jira-cloud/git-commits-issue-tab-and-project-page-gij-cloud) diff --git a/git-integration-for-jira-cloud/git-commits-tab-gij-cloud.md b/git-integration-for-jira-cloud/git-commits-tab-gij-cloud.md index 1de1e14..78ba19d 100644 --- a/git-integration-for-jira-cloud/git-commits-tab-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-commits-tab-gij-cloud.md @@ -13,9 +13,8 @@ The Git Commits tab shows commit information such as commit authors, date of com Open an issue then go to the _**Git Commits**_ tab to view commit information: -| | | | -| --- | --- | --- | | **Pointer** | **Information** | **Description** | +| --- | --- | --- | | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | **Repository/Indexed** | Name of the repository _(as in app config)_ and date of last synchronization with remote repository. | | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | **Author/Committer** | User who performed the commit. Hover the mouse pointer on the name to view user card. | | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | **Issue key/Commit message** | This is the Jira issue with the corresponding commit message. | diff --git a/git-integration-for-jira-cloud/git-integration-configuration-page-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-configuration-page-gij-cloud.md index 2b0a383..10501fa 100644 --- a/git-integration-for-jira-cloud/git-integration-configuration-page-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-configuration-page-gij-cloud.md @@ -15,23 +15,17 @@ On this page, you will be able to setup your git repositories and connect them t * * * -| | -| --- | -| ### Git service integration (Recommended) | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-git-service-sel.png?version=1&modificationDate=1647930706531&cacheVersion=1&api=v2) | -| Formerly known as Full feature auto-connect integration.

Use this type of integration to connect specific git host services to Jira. This integration supports multiple connected repositories and automates most git integration settings.

**We highly recommend this type of integration for multiple repository configuration.**

For more details on supported git host services, see the full feature integration section in our Integration Guides.

**GitLab**
Support for Gitlab API v3 is deprecated. We recommend to use **GitLab API v4** when adding new integrations for increased security. | +### Git service integration (Recommended) +![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-git-service-sel.png?version=1&modificationDate=1647930706531&cacheVersion=1&api=v2) +Formerly known as Full feature auto-connect integration.

Use this type of integration to connect specific git host services to Jira. This integration supports multiple connected repositories and automates most git integration settings.

**We highly recommend this type of integration for multiple repository configuration.**

For more details on supported git host services, see the full feature integration section in our Integration Guides.

**GitLab**
Support for Gitlab API v3 is deprecated. We recommend to use **GitLab API v4** when adding new integrations for increased security. -| | -| --- | -| ### Webhook indexing integration | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-webhook-idx-sel.png?version=1&modificationDate=1647930808726&cacheVersion=1&api=v2) | -| Connect directly to a Git service by configuring webhooks to push commit, branch, pull request, and tag data to Jira Cloud.

Webhook indexing integration allows your connected git servers to work behind a firewall. However, the downside is that your integration will have limited features. For now, the supported git servers are GitHub.com, GitLab and Microsoft. More will be coming in the future. | +### Webhook indexing integration +![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-webhook-idx-sel.png?version=1&modificationDate=1647930808726&cacheVersion=1&api=v2) +Connect directly to a Git service by configuring webhooks to push commit, branch, pull request, and tag data to Jira Cloud.

Webhook indexing integration allows your connected git servers to work behind a firewall. However, the downside is that your integration will have limited features. For now, the supported git servers are GitHub.com, GitLab and Microsoft. More will be coming in the future. -| | -| --- | -| ### Single git repository integration | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-single-repo-sel.png?version=1&modificationDate=1647930891191&cacheVersion=1&api=v2) | -| Manually connect single git repositories using this setup such as git protocol, SSH, HTTP/HTTPS, etc. or simply connect one specific repository. | +### Single git repository integration +![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-single-repo-sel.png?version=1&modificationDate=1647930891191&cacheVersion=1&api=v2) +Manually connect single git repositories using this setup such as git protocol, SSH, HTTP/HTTPS, etc. or simply connect one specific repository. Connected git service integrations appear in the Manage integration configuration list. @@ -44,22 +38,18 @@ Connected git service integrations appear in the Manage integration configuratio * Use the column headers to sort the list in ascending or descending order. -* Use ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Actions** to manage integration/repository settings. +* Use **Actions** to manage integration/repository settings. The above UI descriptions also apply to the Manage repositories page since it has a similar layout. -| | -| --- | -| ### Reindex selected (formerly Reindex All) | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-reindex-all.png?version=1&modificationDate=1647934041821&cacheVersion=1&api=v2) | -| UPDATE
In the new managed user interface, the Reindex all function is further improved and superseded by selecting one or more integration/repositories using the checkboxes and then ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Reindex selected**.

This function will perform a reindex queue of all the selected integration/repository from the list.

**Note**
Reindex will ignore disabled integrations. Enable them first to run reindex on these integrations.


For more information on this topic, see [Reindexing](/git-integration-for-jira-cloud/Reindexing). | - -| | -| --- | -| ### Other features | -| Click the **...** to see other features such as Repository browser and General settings. | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-other-features.png?version=1&modificationDate=1647935460986&cacheVersion=1&api=v2) | -| The rest of the features can also be accessed on the left sidebar. | -| ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923024023/gitcloud-managed-ui-other-features-sidebar.png?version=1&modificationDate=1647935812707&cacheVersion=1&api=v2&width=680&height=413) | +### Reindex selected (formerly Reindex All) +![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-reindex-all.png?version=1&modificationDate=1647934041821&cacheVersion=1&api=v2) +UPDATE
In the new managed user interface, the Reindex all function is further improved and superseded by selecting one or more integration/repositories using the checkboxes and then**Reindex selected**.

This function will perform a reindex queue of all the selected integration/repository from the list.

**Note**
Reindex will ignore disabled integrations. Enable them first to run reindex on these integrations.


For more information on this topic, see [Reindexing](/git-integration-for-jira-cloud/reindexing-gij-cloud) + +### Other features +Click the **...** to see other features such as Repository browser and General settings. +![](https://bigbrassband.atlassian.net/wiki/download/attachments/1923024023/gitcloud-managed-ui-other-features.png?version=1&modificationDate=1647935460986&cacheVersion=1&api=v2) +The rest of the features can also be accessed on the left sidebar +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923024023/gitcloud-managed-ui-other-features-sidebar.png?version=1&modificationDate=1647935812707&cacheVersion=1&api=v2&width=680&height=413) diff --git a/git-integration-for-jira-cloud/git-integration-for-jira-automation-template-library-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-for-jira-automation-template-library-gij-cloud.md index bb649cc..5840001 100644 --- a/git-integration-for-jira-cloud/git-integration-for-jira-automation-template-library-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-for-jira-automation-template-library-gij-cloud.md @@ -61,4 +61,4 @@ We currently support the 5 highlighted triggers depicted below, and we will supp ### Setup: -[Git Integration + Jira Automation](/git-integration-for-jira-cloud/git-integration-jira-automation/) \ No newline at end of file +[Git Integration + Jira Automation](/git-integration-for-jira-cloud/git-integration-jira-automation-gij-cloud) \ No newline at end of file diff --git a/git-integration-for-jira-cloud/git-integration-for-jira-cloud-release-notes-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-for-jira-cloud-release-notes-gij-cloud.md index c0a3657..3ef6763 100644 --- a/git-integration-for-jira-cloud/git-integration-for-jira-cloud-release-notes-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-for-jira-cloud-release-notes-gij-cloud.md @@ -243,7 +243,7 @@ We’ve launched an all-new management user interface, supporting the goal of ma With the [acquisition](https://www.gitkraken.com/blog/gitkraken-acquires-git-integration-jira-bigbrassband) of BigBrassBand's Git Integration for Jira app (GIJ) by GitKraken, we have introduced deep linking between GIJ and GitKraken so users can now have a stronger integration between the two. You can now click to open commits, branches, tags and repositories directly in GitKraken from the Jira issue view giving you a seamless transition from your Jira issues to GitKraken. -[Learn more](/git-integration-for-jira-cloud/deep-linking-to-the-gitkraken-client/) +[Learn more](/git-integration-for-jira-cloud/deep-linking-to-the-gitkraken-client-gij-cloud) You will see the added ability to open the GitKraken client from our app in various locations. See an example of what this looks like below. @@ -261,17 +261,16 @@ You may immediately set the selected branch as default for the current repositor ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/gitcloud-user-settings-create-def-branch-dlg.png?version=2&modificationDate=1632899635182&cacheVersion=1&api=v2&width=340&height=188) -For more information on this feature, see article [Default branch feature](/git-integration-for-jira-cloud/default-branch-feature/). +For more information on this feature, see article [Default branch feature](/git-integration-for-jira-cloud/default-branch-feature-gij-cloud). ## Webhook indexing integration 13 May 2021 NEW FEATURE ADMINS -Webhook indexing integration allows your connected git servers to work behind a firewall but will have limited features which are stated under the Connect the your Git server features comparison table. For detailed information on this new feature, see [Git Integration for Jira Cloud: Webhook indexing integration](/git-integration-for-jira-cloud/webhook-indexing-explainer/). +Webhook indexing integration allows your connected git servers to work behind a firewall but will have limited features which are stated under the Connect the your Git server features comparison table. For detailed information on this new feature, see [Git Integration for Jira Cloud: Webhook indexing integration](/git-integration-for-jira-cloud/webhook-indexing-explainer-gij-cloud). -| | | -| --- | --- | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/gitcloud-release-notes-whook-idx-01.png?version=1&modificationDate=1621314159632&cacheVersion=1&api=v2) | ![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/gitcloud-release-notes-whook-idx-02.png?version=1&modificationDate=1621314164638&cacheVersion=1&api=v2) | +![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/gitcloud-release-notes-whook-idx-01.png?version=1&modificationDate=1621314159632&cacheVersion=1&api=v2) +![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/gitcloud-release-notes-whook-idx-02.png?version=1&modificationDate=1621314164638&cacheVersion=1&api=v2) ## User PATs have been moved to a new page @@ -325,7 +324,7 @@ This information is visible in the native Jira Cloud development information are **Mobile apps** -| | | | +| Examples | Examples | Examples | | --- | --- | --- | | **Jira iOS/Android app: View development information**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/IMG_DCB9B343D5C3-1.jpeg?version=1&modificationDate=1605127361553&cacheVersion=1&api=v2&width=102&height=220) | **Jira iOS/Android app: Branches detail**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/IMG_017E0B3B5371-1.jpeg?version=2&modificationDate=1605127402971&cacheVersion=1&api=v2&width=102&height=220) | **Jira iOS/Android app: Commits detail**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/IMG_80F7BE242631-1.jpeg?version=1&modificationDate=1605127426174&cacheVersion=1&api=v2&width=102&height=220) | | **Jira iOS/Android app: Pull / merge requests detail**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/IMG_2BD0A76A4891-1.jpeg?version=1&modificationDate=1605127449033&cacheVersion=1&api=v2&width=102&height=220) | **Jira iOS/Android app: Git Integration "glance" view**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/IMG_655428BABEEB-1.jpeg?version=1&modificationDate=1605127539872&cacheVersion=1&api=v2&width=102&height=220) | **Jira iOS/Android app: Glance: Create branch**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/IMG_03572F208F3B-1.jpeg?version=1&modificationDate=1605127586708&cacheVersion=1&api=v2&width=102&height=220) | @@ -333,7 +332,7 @@ This information is visible in the native Jira Cloud development information are **MacOS app** -| | | | +| Examples | Examples | Examples | | --- | --- | --- | | **Jira MacOS app: Issue sidebar**

![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20153316@2x-20201111-203318.png?version=1&modificationDate=1605126815417&cacheVersion=1&api=v2) | **Jira MacOS app: Branches detail**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/CleanShot%202020-11-11%20at%20153400@2x-20201111-203401.png?version=1&modificationDate=1605126850897&cacheVersion=1&api=v2&width=204&height=162) | **Jira MacOS app: Commits detail**

![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20153420@2x-20201111-203421.png?version=1&modificationDate=1605126872113&cacheVersion=1&api=v2) | | **Jira MacOS app: Pull / merge requests detail**

![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20153456@2x-20201111-203457.png?version=1&modificationDate=1605126909706&cacheVersion=1&api=v2) | **Jira MacOS app: Git Integration: "glance" view**

![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20153612@2x-20201111-203613.png?version=1&modificationDate=1605126983163&cacheVersion=1&api=v2) | **Jira MacOS app: Git Integration: Glance: Create branch**

![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20153741@2x-20201111-203743.png?version=1&modificationDate=1605127079983&cacheVersion=1&api=v2) | @@ -351,9 +350,9 @@ Developers will often work in a single repository in a given Jira project. Each ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/create-pull-request-annotated.png?version=1&modificationDate=1605045753159&cacheVersion=1&api=v2&width=510&height=190) -Default repository selection for Jira projects is available in the [Create branch](/git-integration-for-jira-cloud/Create-branch) and [Create pull / merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request/) features of the app. +Default repository selection for Jira projects is available in the [Create branch](/git-integration-for-jira-cloud/create-branch-gij-cloud) and [Create pull / merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud) features of the app. -All default selections can be reviewed and updated in [User Settings](/git-integration-for-jira-cloud/User-Settings): +All default selections can be reviewed and updated in [User Settings](/git-integration-for-jira-cloud/user-settings-gij-cloud): ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/user-settings-default.png?version=1&modificationDate=1605564848523&cacheVersion=1&api=v2&width=510&height=246) @@ -365,7 +364,7 @@ All default selections can be reviewed and updated in [User Settings](/git-integ All Jira users with the `View development tools` permission have access to the **Repository browser** screen (_formerly View all repositories_) in Jira Cloud. We have added pagination to this screen to better support large numbers of repositories and the ability to filter the list by search term. -**Note:** Permissions to specific repositories can be limited using Project Permissions (see [Permissions](/git-integration-for-jira-cloud/permissions/) for more information). +**Note:** Permissions to specific repositories can be limited using Project Permissions (see [Permissions](/git-integration-for-jira-cloud/permissions-gij-cloud) for more information). [view-all-repos-pagination-feature.mov](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/view-all-repos-pagination-feature.mov?version=1&modificationDate=1605048187186&cacheVersion=1&api=v2&width=612) @@ -377,7 +376,7 @@ All Jira users with the `View development tools` permission have access to the * ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/871792645/CleanShot%202020-11-05%20at%20132115@2x-20201105-182120.png?version=1&modificationDate=1604600486980&cacheVersion=1&api=v2&width=612&height=428) -The [Webhooks](https://bigbrassband.atlassian.net/git-integration-for-jira-cloud/Webhooks) page now includes logs of inbound webhooks sent to the Git Integration for Jira Cloud app. Status, reindex status, type, and related repository are shown in the table to assist Jira administrators in troubleshooting and identifying which webhooks are triggered for reindexing. +The **Webhooks** page now includes logs of inbound webhooks sent to the Git Integration for Jira Cloud app. Status, reindex status, type, and related repository are shown in the table to assist Jira administrators in troubleshooting and identifying which webhooks are triggered for reindexing. Webhook logs are retained for 7 days. @@ -387,16 +386,14 @@ Webhook logs are retained for 7 days. 28 Feb 2020 NEW FEATURE ALL USERS -When a Jira user creates a pull request or merge request (GitLab) using the Git Integration for Jira app ([Create pull / merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request/)), a link to the Jira issue is included in the pull request / merge request description. +When a Jira user creates a pull request or merge request (GitLab) using the Git Integration for Jira app ([Create pull / merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud), a link to the Jira issue is included in the pull request / merge request description. -| | | | -| --- | --- | --- | | **GitLab** | **GitHub** | **Bitbucket** | +| --- | --- | --- | | ![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20144117@2x-20201111-194133.png?version=1&modificationDate=1605123706591&cacheVersion=1&api=v2) | ![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20144852@2x-20201111-194908.png?version=1&modificationDate=1605124157746&cacheVersion=1&api=v2) | ![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20145222@2x-20201111-195238.png?version=1&modificationDate=1605124390642&cacheVersion=1&api=v2) | -| | | -| --- | --- | | **Azure DevOps** | **AWS Code Commit** | +| --- | --- | | ![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20144156@2x-20201111-194208.png?version=1&modificationDate=1605123738388&cacheVersion=1&api=v2) | ![](https://bigbrassband.atlassian.net/wiki/download/attachments/871792645/CleanShot%202020-11-11%20at%20144604@2x-20201111-194620.png?version=1&modificationDate=1605123984893&cacheVersion=1&api=v2) | * * * diff --git a/git-integration-for-jira-cloud/git-integration-for-jira-home-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-for-jira-home-gij-cloud.md index 7ac091b..63e1d59 100644 --- a/git-integration-for-jira-cloud/git-integration-for-jira-home-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-for-jira-home-gij-cloud.md @@ -14,26 +14,26 @@ Check out the introduction video and links below to get started with GitKraken C ## Getting Started -- [Introduction](/git-integration-for-jira-self-managed/introduction/) - Learn about Git Integration for Jira Cloud. -- [Installation](/git-integration-for-jira-self-managed/installation/) - How to install. -- [Integration Guides](git-integration-for-jira-self-managed/integration-guides/) - All about setting up and using Git Integration for Jira with your preffered git provider. -- [Features](git-integration-for-jira-self-managed/features/) - Learn more about all of the offered features. +- [Introduction](/git-integration-for-jira-cloud/introduction-to-git-integration-gij-cloud) - Learn about Git Integration for Jira Cloud. +- [Installation](/git-integration-for-jira-cloud/installation-and-setup-gij-cloud) - How to install. +- [Integration Guides](/git-integration-for-jira-cloud/integration-guide-gij-cloud) - All about setting up and using Git Integration for Jira with your preffered git provider. +- [Features](/git-integration-for-jira-cloud/features-gij-cloud) - Learn more about all of the offered features. *** ## Knowledgebase -- [Frequently Asked Questions](/git-integration-for-jira-self-managed/frequently-asked-questions/) - Find answers to frequently asked questions. -- [How-to Articles](/git-integration-for-jira-self-managed/how-to-articles/) - Learn how to do common setups and workflows. -- [Troubleshooting](/git-integration-for-jira-self-managed/troubleshooting-articles/) - In-depth articles to help you diagnose and solve problems. -- [Known Issues](/git-integration-for-jira-self-managed/known-issues/) - problems that occur with some configurations their accompanying workarounds. -- [Hooks and Webhooks](git-integration-for-jira-self-managed/hooks-and-webhooks/) - all about hooks! +- [Frequently Asked Questions](/git-integration-for-jira-cloud/frequently-asked-questions-gij-cloud) - Find answers to frequently asked questions. +- [How-to Articles](/git-integration-for-jira-cloud/how-to-articles-gij-cloud) - Learn how to do common setups and workflows. +- [Troubleshooting](/git-integration-for-jira-cloud/troubleshooting-articles-gij-cloud) - In-depth articles to help you diagnose and solve problems. +- [Known Issues](/git-integration-for-jira-cloud/known-issues-gij-cloud) - problems that occur with some configurations their accompanying workarounds. +- [Hooks and Webhooks](/git-integration-for-jira-cloud/hooks-and-webhooks-gij-cloud) - all about hooks! *** ## Additional Resources -- [Video Guides](/git-integration-for-jira-self-managed/git-integration-jira-data-center-video-guides/) - List of video guides to aid you in your Git Integration for Jira journey. +- [Video Guides](/git-integration-for-jira-cloud/git-integration-jira-cloud-video-guides-gij-cloud) - List of video guides to aid you in your Git Integration for Jira journey. - [Version History](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira/version-history) - Find out what changes were implemented when. Join our GitKraken public slack community and interact with other Git Integration for Jira users from around the world 🌐. diff --git a/git-integration-for-jira-cloud/git-integration-jira-automation-advanced-examples-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-jira-automation-advanced-examples-gij-cloud.md index d1501e1..179b999 100644 --- a/git-integration-for-jira-cloud/git-integration-jira-automation-advanced-examples-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-jira-automation-advanced-examples-gij-cloud.md @@ -8,15 +8,15 @@ taxonomy: --- [Git Integration + Jira Automation](/git-integration-for-jira-cloud/git-integration-jira-automation/)> Advanced Examples -| | | -| --- | --- | -| ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-branch-01.png?version=4&modificationDate=1623408549068&cacheVersion=1&api=v2&width=321&height=413) | ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-commit-01.png?version=2&modificationDate=1623408300311&cacheVersion=1&api=v2&width=313&height=411) | -| ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-pullreq-01.png?version=2&modificationDate=1623408456713&cacheVersion=1&api=v2&width=324&height=447) | ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-pullreq-02.png?version=2&modificationDate=1623408717252&cacheVersion=1&api=v2&width=340&height=462) | -| ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-branch-conditional-01.png?version=2&modificationDate=1623408867352&cacheVersion=1&api=v2&width=330&height=636) | ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-issue-condition-01.png?version=2&modificationDate=1623409029439&cacheVersion=1&api=v2&width=322&height=563) | +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-branch-01.png?version=4&modificationDate=1623408549068&cacheVersion=1&api=v2&width=321&height=413) +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-commit-01.png?version=2&modificationDate=1623408300311&cacheVersion=1&api=v2&width=313&height=411) +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-pullreq-01.png?version=2&modificationDate=1623408456713&cacheVersion=1&api=v2&width=324&height=447) +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-pullreq-02.png?version=2&modificationDate=1623408717252&cacheVersion=1&api=v2&width=340&height=462) +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-branch-conditional-01.png?version=2&modificationDate=1623408867352&cacheVersion=1&api=v2&width=330&height=636) +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1714257921/automation-issue-condition-01.png?version=2&modificationDate=1623409029439&cacheVersion=1&api=v2&width=322&height=563) ### More Jira automation information -![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) [Automation basics](https://www.atlassian.com/software/jira/guides/expand-jira/automation) -![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) [What are smart values?](https://support.atlassian.com/jira-software-cloud/docs/what-are-smart-values/) -![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) [Automation conditions](https://support.atlassian.com/jira-software-cloud/docs/automation-conditions/) -![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) \ No newline at end of file +[Automation basics](https://www.atlassian.com/software/jira/guides/expand-jira/automation) +[What are smart values?](https://support.atlassian.com/jira-software-cloud/docs/what-are-smart-values/) +[Automation conditions](https://support.atlassian.com/jira-software-cloud/docs/automation-conditions/) diff --git a/git-integration-for-jira-cloud/git-integration-jira-automation-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-jira-automation-gij-cloud.md index 8f0daf3..f2d093b 100644 --- a/git-integration-for-jira-cloud/git-integration-jira-automation-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-jira-automation-gij-cloud.md @@ -50,13 +50,13 @@ Create a rule to configure triggers and actions for automating tasks. There are ### Project level (projects) -1. Open a project to work on, then go to ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Project settings**. +1. Open a project to work on, then go to **Project settings**. 2. ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1698922497/gitcloud-automation-proj-level-02(c).png?version=2&modificationDate=1632383594084&cacheVersion=1&api=v2) On the sidebar, click **Automation**. -3. Click the ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Rules** tab. +3. Click the **Rules** tab. 4. Click **Create rule** to create a new automation rule. @@ -86,7 +86,7 @@ Create a rule to configure triggers and actions for automating tasks. There are 3. ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1698922497/gitcloud-automation-proj-level-02(c).png?version=2&modificationDate=1632383594084&cacheVersion=1&api=v2) - Click the ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Rules** tab. + Click the **Rules** tab. 4. Click **Create rule** to create a new automation rule. @@ -113,5 +113,5 @@ Create a rule to configure triggers and actions for automating tasks. There are ## Advanced Examples -For advanced examples, see sub-page [Automation Advanced Examples](/git-integration-for-jira-cloud/git-integration-jira-automation-advanced-examples/). +For advanced examples, see sub-page [Automation Advanced Examples](/git-integration-for-jira-cloud/git-integration-jira-automation-advanced-examples-gij-cloud). diff --git a/git-integration-for-jira-cloud/git-integration-jira-cloud-video-guides-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-jira-cloud-video-guides-gij-cloud.md index d56a41f..7304aee 100644 --- a/git-integration-for-jira-cloud/git-integration-jira-cloud-video-guides-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-jira-cloud-video-guides-gij-cloud.md @@ -110,4 +110,4 @@ Setup GitLab server personal access tokens and scopes required for Git for Jira **[Receive App Update Notifications »](https://bigbrassband.wistia.com/medias/u9rojnv0vv)** -Configure Jira preferences to enable receiving of app update notifications. \ No newline at end of file +Configure Jira preferences to enable receiving of app update notifications. diff --git a/git-integration-for-jira-cloud/git-integration-options-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-options-gij-cloud.md index 159c6e0..fb0e944 100644 --- a/git-integration-for-jira-cloud/git-integration-options-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-options-gij-cloud.md @@ -7,7 +7,7 @@ taxonomy: --- -This setting is part of the [**General Settings**](/git-integration-for-jira-cloud/General-Settings) configuration page for Git Integration for Jira Cloud. +This setting is part of the [**General Settings**](/git-integration-for-jira-cloud/general-settings-gij-cloud) configuration page for Git Integration for Jira Cloud. These settings will take effect at integration level for projects with connected GitLab/GitHub git hosts. The default state for each setting is _enabled_. @@ -19,12 +19,10 @@ These settings will take effect at integration level for projects with connected ## Git integration settings -| | -| --- | -| ### Enable create \| delete branch | -| This setting shows or hides the function for creating/deleting of branches. The ability to create/delete selected branches from the Jira developer panel is dependent on this setting.

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1207829137/gitcloud-dev-panel-create-branch-sel.png?version=1&modificationDate=1643340514593&cacheVersion=1&api=v2&width=296&height=208) | -| ### Enable create pull \| merge request | -| This setting shows or hides the function for creating pull/merge requests from the Jira developer panel.

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1207829137/gitcloud-dev-panel-create-PRMR-sel.png?version=1&modificationDate=1643340576227&cacheVersion=1&api=v2&width=296&height=208) | +### Enable create \ delete branch +This setting shows or hides the function for creating/deleting of branches. The ability to create/delete selected branches from the Jira developer panel is dependent on this setting.

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1207829137/gitcloud-dev-panel-create-branch-sel.png?version=1&modificationDate=1643340514593&cacheVersion=1&api=v2&width=296&height=208) +### Enable create pull \ merge request +This setting shows or hides the function for creating pull/merge requests from the Jira developer panel.

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1207829137/gitcloud-dev-panel-create-PRMR-sel.png?version=1&modificationDate=1643340576227&cacheVersion=1&api=v2&width=296&height=208) ## Branch name template @@ -34,15 +32,14 @@ Set the **Branch Name Template** using the supported variables. Use the templa Use the following template variables: -| | -| --- | -| `${issuetype}` – Issue Type. The Issue type is used to map a custom issue type as part of the template. The mapping pattern should look like this:

```java
${issuetype:type0,subsitute0[,type1,substitute1,...,typeN,substituteN][,defaultsubstitute]}
```

* `typeN` - is the _**nth**_ issue type string to match.

* `substituteN` - is the substitution string to use for _**typeN**_.

* `defaultsubstitute` - is the substitution string to use if _**typeN**_'s match is not found. If _**defaultsubstitute**_ is blank, the lowercase version of the defined issue type is used. | -| `${issuekey}` – Issue Key. The Issue key is used in upper case. | -| `${summary}` – Issue Summary. The Summary is used from the current Jira issue your are on and will be in lowercase; spaces are substituted by "-" (dash). | -| **The Git Integration for Jira app default is:**
`${issuekey}-${summary}`

This generates the string format like "**PRJ-123-add-more-logging**" as a default value for the Create Branch and Pull/Merge Request dialogs. Where `PRJ-123` is the issue key followed by a hyphen then the summary text of the active issue page (in hyphenated lowercase form). | -| `${sourcebranch}` – Source branch. The source branch from the Create Branch dialog is used and will be in lowercase; spaces are substituted by "-" (dash). | -| `${projectkey}` – Project Key. The Project key is used and will be in uppercase. | -| `${displayname}` -- This is the displayed name of the current user. | +`${issuetype}` – Issue Type. The Issue type is used to map a custom issue type as part of the template. The mapping pattern should look like this:

```java
${issuetype:type0,subsitute0[,type1,substitute1,...,typeN,substituteN][,defaultsubstitute]}
```

* `typeN` - is the _**nth**_ issue type string to match.

* `substituteN` - is the substitution string to use for _**typeN**_.

* `defaultsubstitute` - is the substitution string to use if _**typeN**_'s match is not found. If _**defaultsubstitute**_ is blank, the lowercase version of the defined issue type is used. +`${issuekey}` – Issue Key. The Issue key is used in upper case. +`${summary}` – Issue Summary. The Summary is used from the current Jira issue your are on and will be in lowercase; spaces are substituted by "-" (dash). +**The Git Integration for Jira app default is:**
`${issuekey}-${summary}`

This generates the string format like "**PRJ-123-add-more-logging**" as a default value for the Create Branch and Pull/Merge Request dialogs. Where `PRJ-123` is the issue key followed by a hyphen then the summary text of the active issue page (in hyphenated lowercase form). +`${sourcebranch}` – Source branch. The source branch from the Create Branch dialog is used and will be in lowercase; spaces are substituted by "-" (dash). +`${projectkey}` – Project Key. The Project key is used and will be in uppercase. +`${displayname}` -- This is the displayed name of the current user. + ## Branch name templates inner separator @@ -60,21 +57,18 @@ This setting allows administrators to specify the maximum character length for b ## Some examples -| | -| --- | | **Example 1:** | +| --- | | `${issuetype}/${issuekey}-${summary}` | | This generates the string format like "**newfeature/PRJ-123-add-more-logging**" as a default value for the branch names. Where `newfeature` is the actual issue type of the active Jira issue; in lowercase and trimmed of whitespaces, `PRJ-123` is the issue key followed by a hyphen then the summary text of the active issue page (in hyphenated lowercase form). | -| | -| --- | | **Example 2:** | +| --- | | `${issuetype:New Feature,feature,Bug Fix,bug}/${issuekey}-${summary}` | | This generates the string format like "**feature/PRJ-123-add-more-logging**" as a default value for the branch names. This example uses a Jira issue which has the _**New Feature**_ issue type -- where `feature` is the substituted to _issuetype_ since _type0_ matches the active Jira issue type; `PRJ-123` is the issue key followed by a hyphen then the summary text of the active issue page (in hyphenated lowercase form). | -| | -| --- | | **Example 3:** | +| --- | | `${issuetype:Old Issue,old,Bug Fix,bug,branch}/${issuekey}-${summary}` | | This generates the string format like "**branch/PRJ-123-add-more-logging**" as a default value for the branch names. This example uses a Jira issue which has the _**New Feature**_ issue type -- where `branch` is substituted to _issuetype_ since _type0..typeN_ does not match the active Jira issue type; `PRJ-123` is the issue key followed by a hyphen then the summary text of the active issue page (in hyphenated lowercase form). | diff --git a/git-integration-for-jira-cloud/git-integration-server-data-center-vs-jira-cloud-feature-comparison-gij-cloud.md b/git-integration-for-jira-cloud/git-integration-server-data-center-vs-jira-cloud-feature-comparison-gij-cloud.md index f314673..a18da0f 100644 --- a/git-integration-for-jira-cloud/git-integration-server-data-center-vs-jira-cloud-feature-comparison-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-integration-server-data-center-vs-jira-cloud-feature-comparison-gij-cloud.md @@ -10,19 +10,26 @@ See also [Feature matrix of Git Integration for Jira Cloud](/git-integration-for We publish roadmaps for [**Jira Cloud**](https://trello.com/b/Af64QYkE/git-integration-jira-cloud-roadmap) and [**Jira Server + Data Center**](https://trello.com/b/WRrWMs87/git-integration-server-data-center-roadmap). If you have questions about specific differences between Jira Server + Data Center and Jira Cloud - [contact us through our support desk](https://bigbrassband.atlassian.net/servicedesk/customer/portals). -| | | | +## Features +| **Features** | **Git Integration for Jira Server** and
**Git Integration for Jira Data Center** | **Git Integration for Jira Cloud** | | --- | --- | --- | -| ## **Features** | **Git Integration for Jira Server** and
**Git Integration for Jira Data Center** | **Git Integration for Jira Cloud** | | **Reindexing** | Jira administrator controlled | Automatic | | **Automatic workflow triggers \*** | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **\*** | | **Disable indexing** | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | * Individual repositories | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | * Individual integrations | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | + +### Reindexing + | **Manual reindexing of all integrations/repositories** | | | +| --- | --- | --- | | * Individual repositories (if configured as plain git) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | * Individual integrations | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | * All repositories + integrations | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | + +### Repository Browser | **Repository Browser** | | | +| --- | --- | --- | | * Browse | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | * Commits | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | * Compare | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | @@ -69,7 +76,10 @@ We publish roadmaps for [**Jira Cloud**](https://trello.com/b/Af64QYkE/git-integ | * Audit log settings | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | **Activity Stream** 2 | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | **JQL** 3 | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **\*** | + +### Webhooks | **Webhooks** | | | +| --- | --- | --- | | * Reindex all repositories | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | * Reindex integrations | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | * Reindex repositories | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | @@ -102,13 +112,13 @@ We publish roadmaps for [**Jira Cloud**](https://trello.com/b/Af64QYkE/git-integ | **View Code Diffs in Jira** **6** | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | | Code expanders to see context of changes in diff screen | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) | -**\*** Requires [Jira Development Information](/wiki/spaces/GITCLOUD/pages/138772493/Jira+Development+Information) to be enabled in the [General settings](/git-integration-for-jira-cloud/General-Settings). +**\*** Requires [Jira Development Information](/git-integration-for-jira-cloud/jira-development-information-gij-cloud) to be enabled in the [General settings](/git-integration-for-jira-cloud/general-settings-gij-cloud). **1** See information for self-hosted git servers in Jira Cloud below: When connecting a self-hosted git server to [**Git Integration for Jira Cloud**](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=overview), the git server must have a publicly addressable + route-able address. For example, [GitHub.com](http://github.com/), [https://dev.azure.com](https://dev.azure.com/), [GitLab.com](http://gitlab.com/) and other services hosted on the "public cloud" work without any administrator interventions. -For more information, see [Whitelist BigBrassBand Cloud](/git-integration-for-jira-cloud/allow-list-whitelist-bigbrassband-cloud/). +For more information, see [Whitelist BigBrassBand Cloud](/git-integration-for-jira-cloud/allow-list-whitelist-bigbrassband-cloud-gij-cloud). **2** No support on Jira Cloud for third-party publishing to Jira Activity Stream. @@ -130,9 +140,9 @@ For more information, see [Whitelist BigBrassBand Cloud](/git-integration-for-ji * `development[pullrequests].open> 0` -**4** GIT INTEGRATION: JIRA CLOUD Smart commit email notifications will fail when using [Jira Development Information](/git-integration-for-jira-cloud/jira-development-information/). +**4** GIT INTEGRATION: JIRA CLOUD Smart commit email notifications will fail when using [Jira Development Information](/git-integration-for-jira-cloud/jira-development-information-gij-cloud). -**5** GIT INTEGRATION: JIRA CLOUD [Jira Development Information](/git-integration-for-jira-cloud/jira-development-information/) is not controlled by Project Permissions. +**5** GIT INTEGRATION: JIRA CLOUD [Jira Development Information](/git-integration-for-jira-cloud/jira-development-information-gij-cloud) is not controlled by Project Permissions. **6** See notes below: diff --git a/git-integration-for-jira-cloud/git-roll-up-issue-tab-gij-cloud.md b/git-integration-for-jira-cloud/git-roll-up-issue-tab-gij-cloud.md index ae97e51..d57244b 100644 --- a/git-integration-for-jira-cloud/git-roll-up-issue-tab-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-roll-up-issue-tab-gij-cloud.md @@ -49,4 +49,5 @@ Some notable sections: ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/138510337/gitcloud-gencfg-git-rollup-sel.png?version=1&modificationDate=1638616220087&cacheVersion=1&api=v2&width=680&height=250) **Contact Us** -If you still have a question - reach out to our [Support Desk](https://bigbrassband.atlassian.net/servicedesk/customer/portals) or email us at [support@bigbrassband.com](mailto:support@bigbrassband.com) \ No newline at end of file +If you still have a question - reach out to our [Support Desk](https://bigbrassband.atlassian.net/servicedesk/customer/portals) or email us at [support@bigbrassband.com](mailto:support@bigbrassband.com) + diff --git a/git-integration-for-jira-cloud/git-roll-up-issue-tab-setting-gij-cloud.md b/git-integration-for-jira-cloud/git-roll-up-issue-tab-setting-gij-cloud.md index 352d783..fb4562e 100644 --- a/git-integration-for-jira-cloud/git-roll-up-issue-tab-setting-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-roll-up-issue-tab-setting-gij-cloud.md @@ -7,7 +7,7 @@ taxonomy: --- -This setting is part of the [**General settings**](/git-integration-for-jira-cloud/General-Settings) configuration page for Git Integration for Jira Cloud. +This setting is part of the [**General settings**](/git-integration-for-jira-cloud/general-settings-gij-cloud) configuration page for Git Integration for Jira Cloud. **Default settings** This setting is enabled in [**Git Integration for Jira Cloud**](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?tab=overview&hosting=cloud) app by default. @@ -19,7 +19,7 @@ This setting is turned off by default in [**Dev Info for Jira Cloud**](https:// The Git Roll Up Issue tab displays a summary of the files, lines and the developers who made the changes in the commits commits associated with the Jira issue. Enable/disable this setting to allow the **Git Roll Up** tab on the Issue page for all Jira projects. -For more details, see [**Features: Git Roll Up tab (Jira Cloud)**](/git-integration-for-jira-cloud/git-roll-up-issue-tab/). +For more details, see [**Features: Git Roll Up tab (Jira Cloud)**](/git-integration-for-jira-cloud/git-roll-up-tab-gij-cloud). **Permissions** The **View developer tools** _permission_ is required to view the Git Roll Up Issue Tab. Jira users must also have the **Browse Project** _permissions_ to a project associated with a repository to view. diff --git a/git-integration-for-jira-cloud/git-roll-up-tab-gij-cloud.md b/git-integration-for-jira-cloud/git-roll-up-tab-gij-cloud.md index 02b05a2..d23a49f 100644 --- a/git-integration-for-jira-cloud/git-roll-up-tab-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-roll-up-tab-gij-cloud.md @@ -18,9 +18,9 @@ Open a Jira issue then go to the Git Roll Up tab to view commit statistics, di Sort the code statistics by clicking the respective **Sort** button then selecting the required sorting option. -| | | -| --- | --- | -| ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923025721/gitcloud-git-rollup-sort01.png?version=1&modificationDate=1635417146113&cacheVersion=1&api=v2&width=168&height=228) | ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923025721/gitcloud-git-rollup-sort02.png?version=1&modificationDate=1635417306092&cacheVersion=1&api=v2&width=168&height=288) | +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923025721/gitcloud-git-rollup-sort01.png?version=1&modificationDate=1635417146113&cacheVersion=1&api=v2&width=168&height=228) + +![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923025721/gitcloud-git-rollup-sort02.png?version=1&modificationDate=1635417306092&cacheVersion=1&api=v2&width=168&height=288) Select roll up options by clicking the respective **Rollup** button. diff --git a/git-integration-for-jira-cloud/git-services-support-page-and-end-of-life-policies-gij-cloud.md b/git-integration-for-jira-cloud/git-services-support-page-and-end-of-life-policies-gij-cloud.md index c89bbfe..b865b60 100644 --- a/git-integration-for-jira-cloud/git-services-support-page-and-end-of-life-policies-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-services-support-page-and-end-of-life-policies-gij-cloud.md @@ -8,15 +8,15 @@ taxonomy: --- Git Integration for Jira app currently supports all the cloud hosted versions and the officially supported versions of the self-hosted git services: -* [GitHub Enterprise](/git-integration-for-jira-cloud/github-enterprise-eol/) +* [GitHub Enterprise](/git-integration-for-jira-cloud/github-enterprise-eol-gij-cloud) -* [GitLab CE/EE](/git-integration-for-jira-cloud/gitlab-ce-ee-eol-support-policy/) +* [GitLab CE/EE](/git-integration-for-jira-cloud/gitlab-ce-ee-gij-cloud) -* [Bitbucket Server/Cloud](/git-integration-for-jira-cloud/bitbucket-server-cloud-eol-support-policy/) +* [Bitbucket Server/Cloud](/git-integration-for-jira-cloud/bitbucket-server-cloud-eol-support-policy-gij-cloud) -* [Azure DevOps Server / TFS](/git-integration-for-jira-cloud/azure-devops-server-lifecycle-policies/) +* [Azure DevOps Server / TFS](/git-integration-for-jira-cloud/azure-devops-server-lifecycle-policies-gij-cloud) -* [Gerrit](/git-integration-for-jira-cloud/gerrit-end-of-life/) +* [Gerrit](/git-integration-for-jira-cloud/gerrit-end-of-life-gij-cloud) Most offered services have their own End-of-Life (EOL) policies that ranges from one year or more. For most cases, it’s generally one year following its release date. \ No newline at end of file diff --git a/git-integration-for-jira-cloud/git-tags-gij-cloud.md b/git-integration-for-jira-cloud/git-tags-gij-cloud.md index ec9d961..57597b7 100644 --- a/git-integration-for-jira-cloud/git-tags-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-tags-gij-cloud.md @@ -69,4 +69,4 @@ Move the mouse pointer over the tag to display the following tooltip information Tags are only associated with the Jira issue by Jira keys that are specified in commits that belong to the tag. Specifying a Jira key in the name of a tag does not associate this tag with the mentioned ticket. -If some commits relate only to tags, these commits will not be displayed. For more information, see the [related known issue](/git-integration-for-jira-cloud/known-issues/). +If some commits relate only to tags, these commits will not be displayed. For more information, see the [related known issue](/git-integration-for-jira-cloud/known-issues-gij-cloud). diff --git a/git-integration-for-jira-cloud/git-url-ports-gij-cloud.md b/git-integration-for-jira-cloud/git-url-ports-gij-cloud.md index ad0b318..0e27a45 100644 --- a/git-integration-for-jira-cloud/git-url-ports-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-url-ports-gij-cloud.md @@ -10,9 +10,8 @@ If your Git servers are running through a firewall, configure the firewall to al Below are the default ports for common git URL protocols: -| | | -| --- | --- | | **Protocol** | **Default Port** | +| --- | --- | | ssh:// | port 22 | | git:// | port 9418 | | http:// | port 80 | @@ -30,4 +29,4 @@ Test git connection and repository URL by doing the following: The Git Integration for Jira app will run successfully if the above connection test ran without errors. -For detailed information on whitelisting your Git server, see [Allow list (whitelist) BigBrassBand Cloud](/git-integration-for-jira-cloud/allow-list-whitelist-bigbrassband-cloud/). +For detailed information on whitelisting your Git server, see [Allow list (whitelist) BigBrassBand Cloud](/git-integration-for-jira-cloud/allow-list-whitelist-bigbrassband-cloud-gij-cloud). diff --git a/git-integration-for-jira-cloud/git-user-identity-gij-cloud.md b/git-integration-for-jira-cloud/git-user-identity-gij-cloud.md index cb65859..0353366 100644 --- a/git-integration-for-jira-cloud/git-user-identity-gij-cloud.md +++ b/git-integration-for-jira-cloud/git-user-identity-gij-cloud.md @@ -34,3 +34,5 @@ Hosting services _(like GitHub and BitBucket, for example)_ try to match these The Git Integration for Jira app will use the email from a commit and will search for a Jira user using this email. If the Jira user is found, the associated link to his Jira profile is displayed with the accompanying Jira avatar beside the name. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1923023946/image-20210728-082525.png?version=1&modificationDate=1630063581337&cacheVersion=1&api=v2&width=421&height=69) + + diff --git a/git-integration-for-jira-cloud/github-com-gij-cloud.md b/git-integration-for-jira-cloud/github-com-gij-cloud.md index 1aaee41..f3bfcc4 100644 --- a/git-integration-for-jira-cloud/github-com-gij-cloud.md +++ b/git-integration-for-jira-cloud/github-com-gij-cloud.md @@ -10,7 +10,7 @@ These instructions apply to instances on Free, Team, Cloud Enterprise (including For instructions on self-hosted GitHub Enterprise Server, please see [this page](#). -Using **Jira Server or Data Center**? [See the corresponding article](https://bigbrassband.atlassian.net/wiki/x/igBNAw). +Using **Jira Server or Data Center**? [See the corresponding article](/git-integration-for-jira-self-managed/github-gij-self-managed). ![GitHub Banner logo](https://bigbrassband.com/confluence/images/github-logo.svg) @@ -29,7 +29,7 @@ _(Updated video coming soon)_ If two-factor authentication is enabled for your GitHub account, you will need to create a personal access token (PAT) to access your git repositories. Enable two-factor authentication in your GitHub.com account for increased security. -While instructions from GitHub works just fine, please [follow this article](/git-integration-for-jira-cloud/creating-personal-access-tokens/) for a quick step-by-step guide to get you started. +While instructions from GitHub works just fine, please [follow this article](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud) for a quick step-by-step guide to get you started. ## Using Git service integration @@ -60,11 +60,11 @@ We strongly recommend to use personal access tokens for GitHub.com account integ ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/82477058/gitcloud-integration-advanced-options-wo-sslverify(c).png?version=1&modificationDate=1649313273881&cacheVersion=1&api=v2&width=510&height=266) * **Custom API Path** – his is a relative path that starts with "/". The integration will use the relative REST API path to retrieve the list of tracked repositories. The maximum allowed length is 2000 characters or less. - To learn more examples, see article [Jira Cloud: Working with Custom API Path](http://bigbrassband.atlassian.net/wiki/spaces/GITCLOUD/pages/133201972/Working+with+Custom+API+Path). + To learn more examples, see article [Jira Cloud: Working with Custom API Path](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud). * **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. Read about JMESPath expressions on their [website](http://jmespath.org/). For help with writing expressions, please contact [support](mailto:support@bigbrassband.com). - To learn more examples, see article [Jira Cloud: Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters/). + To learn more examples, see article [Jira Cloud: Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud). 2. While Custom API Path and JMESPath filter are mutually exclusive, you can use one, the other, both or neither. @@ -111,9 +111,9 @@ This process requires an existing GitHub git repository. Look for the the GitHu Use this information to connect the GitHub git repository to your Jira Cloud via Git Integration for Jira app: -[Single git repository integration (HTTPS)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-http-https/) +[Single git repository integration (HTTPS)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-http-https-gij-cloud) -[Single git repository integration (SSH)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-ssh/) +[Single git repository integration (SSH)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-ssh-gij-cloud) ## Setting up GitHub permissions @@ -125,7 +125,7 @@ Assign GitHub permissions for team members or collaborators to allow which resou 1. Login to your GitHub.com account. -2. Go to ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Profile** ➜ **Settings**. +2. Go to **Profile** ➜ **Settings**. 3. On your sidebar, click **Organizations**. @@ -198,7 +198,7 @@ The Git Integration for Jira app automatically configures web linking for GitHub 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](/git-integration-for-jira-cloud/Web-linking). +For more information on this feature, see [Documentation: Web linking](/git-integration-for-jira-cloud/web-linking-gij-cloud). ## Viewing git commits in Jira Cloud @@ -211,7 +211,7 @@ For more information on this feature, see [Documentation: Web linking](/git-inte 4. Click **View full commit** to view the code diff. -For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues/). +For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues-gij-cloud). ## Working with branches and pull requests with GitHub @@ -244,7 +244,7 @@ On your Jira Cloud, open a Jira issue. On the Jira Git integration development p 4. Click **Create branch** to complete this process. -For more detailed information on this feature, see [Create branch](/git-integration-for-jira-cloud/Create-branch). +For more detailed information on this feature, see [Create branch](/git-integration-for-jira-cloud/create-branch-gij-cloud). The newly-created branch is now listed in the Jira developer panel under **Branches**. Perform a commit to the newly-created branch to be ready for merge. @@ -267,7 +267,7 @@ The pull request feature works the same as merge request. On your Jira Cloud, op 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](#) page. -2. Choose the newly-created branch as the **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one repository - use the [User settings](#) page. +2. Choose the newly-created branch as the **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one repository - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. 3. Set _**master**_ as the **Target branch**. @@ -280,7 +280,7 @@ Pull/merge requests are still indexed based on branch name even if the PR/MR tit **Preview** allows you to see the comparison view of the current changes in the selected **Source branch** vs **Target branch** (_usually_ _master_). -For more detailed information on this feature, see [Create pull/merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request/). +For more detailed information on this feature, see [Create pull/merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud). The pull request is listed on the developer panel of the Jira issue page. diff --git a/git-integration-for-jira-cloud/github-com-github-enterprise-jmespath-filter-examples-gij-cloud.md b/git-integration-for-jira-cloud/github-com-github-enterprise-jmespath-filter-examples-gij-cloud.md index 90156d7..92e9034 100644 --- a/git-integration-for-jira-cloud/github-com-github-enterprise-jmespath-filter-examples-gij-cloud.md +++ b/git-integration-for-jira-cloud/github-com-github-enterprise-jmespath-filter-examples-gij-cloud.md @@ -11,21 +11,18 @@ taxonomy: An optional JMESPath filter can be configured when adding GitHub integration or repositories. -| | -| --- | | **1\. Contains (include)** | +| --- | | ```java
[?contains(name, 'git')]
``` | | This is a filter based on the text in the repository name. It will list repositories with names that contain the word `'git'`. Do note that the declared string format is case-sensitive. | -| | -| --- | | **2\. Starts with or ends with** | +| --- | | ```java
[?starts_with(name, 'git') \| ends_with(name, 'test')]
``` | | Lists repositories with names that starts with `'git'` or ends with `'test'`. | -| | -| --- | | **3\. Contains (exclude)** | +| --- | | ```java
[?(!contains(name, 'firstword'))]
[?(!contains(name, 'firstword')) \| (!contains(name, 'secondword'))]
``` | | 1 – Lists repositories with names that either do not contain the word `'firstword'`.
2 – Lists repositories with names that either do not contain the words `‘firstword’` OR `‘secondword’`. | | The `!condition` must be wrapped in a parenthesis so it won’t invert the whole expression. | diff --git a/git-integration-for-jira-cloud/github-enterprise-eol-gij-cloud.md b/git-integration-for-jira-cloud/github-enterprise-eol-gij-cloud.md index d4d1a7c..3af2577 100644 --- a/git-integration-for-jira-cloud/github-enterprise-eol-gij-cloud.md +++ b/git-integration-for-jira-cloud/github-enterprise-eol-gij-cloud.md @@ -10,4 +10,5 @@ The End-of-life (EOL) for a major release of GitHub Enterprise server is general For example, GitHub Enterprise Server 2.16.0 was released on January 22, 2019 and had an EOL date of January 22, 2020. Similarly, 2.17.0 was released on May 23, 2019 and had an EOL date of May 23, 2020. -GitHub’s [**Releases page**](https://enterprise.github.com/releases) can be used to get these dates, as well as release notes for any given version. EOL notices are also published [at the top of documentation pages](https://docs.github.com/en/enterprise/2.17) for their respective version, as well as in the [**Release notes** for patches leading up to EOL](https://enterprise.github.com/releases/2.17.25/notes). \ No newline at end of file +GitHub’s [**Releases page**](https://enterprise.github.com/releases) can be used to get these dates, as well as release notes for any given version. EOL notices are also published [at the top of documentation pages](https://docs.github.com/en/enterprise/2.17) for their respective version, as well as in the [**Release notes** for patches leading up to EOL](https://enterprise.github.com/releases/2.17.25/notes). + diff --git a/git-integration-for-jira-cloud/github-enterprise-server-gij-cloud.md b/git-integration-for-jira-cloud/github-enterprise-server-gij-cloud.md index cae064d..9ad165f 100644 --- a/git-integration-for-jira-cloud/github-enterprise-server-gij-cloud.md +++ b/git-integration-for-jira-cloud/github-enterprise-server-gij-cloud.md @@ -10,7 +10,7 @@ These instructions apply to self-hosted GitHub Enterprise Server. For instructions to instances hosted on GitHub.com (Free, Team, Enterprise (including [**EMU**](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)) plans), please go to [this page](/wiki/spaces/GITCLOUD/pages/82477058/GitHub.com). -Using **Jira Server or Data Center**? [See the corresponding article](/git-integration-for-jira-self-managed/github-enterprise-server/). +Using **Jira Server or Data Center**? [See the corresponding article](/git-integration-for-jira-self-managed/github-enterprise-server-gij-self-managed). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/85622870/github-ent-server-banner-logo.png?version=1&modificationDate=1646820087185&cacheVersion=1&api=v2&width=510&height=59) @@ -29,7 +29,7 @@ _Right click_ [_**here**_](https://bigbrassband.wistia.com/medias/vfwwqnn3mm) _a If two-factor authentication is enabled for your GitHub Enterprise Server account, you will need to create a personal access token (PAT) to access your git repositories. Enable two-factor authentication in your GitHub Enterprise Server account for increased security. -While instructions from GitHub works just fine, [follow this article](/git-integration-for-jira-cloud/creating-personal-access-tokens/) for a quick step-by-step guide to get you started. +While instructions from GitHub works just fine, [follow this article](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud) for a quick step-by-step guide to get you started. ## Using Git service integration @@ -64,11 +64,11 @@ We recommend using the **Git service integration** panel to connect multiple rep 1. **SSL Verify** – The **SSL Verify** option is set to `Enabled` by default. If set to `Disabled`, the Git Integration for Jira Cloud app will ignore verification of SSL certificates when connecting to a git server. _This option is not available for non-fetched repositories._ 2. **Custom API Path** – this 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. - To learn more examples, see article [Jira Cloud: Working with Custom API Path](/git-integration-for-jira-cloud/working-with-custom-api-path/). + To learn more examples, see article [Jira Cloud: Working with Custom API Path](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud). 3. **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. Read about JMESPath expressions on their [website](http://jmespath.org/). For help with writing expressions, please contact [support](mailto:support@bigbrassband.com). - To learn more examples, see article [Jira Cloud: Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters/). + To learn more examples, see article [Jira Cloud: Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud). 4. While Custom API Path and JMESPath filter are mutually exclusive, you can use one, the other, both or neither. @@ -96,7 +96,7 @@ This process requires an existing GitHub Enterprise Server git repository. Look Use this information to connect the GitHub git repository to your Jira Cloud via Git Integration for Jira app: -[Single git repository integration (HTTPS)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-http-https/) +[Single git repository integration (HTTPS)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-http-https-gij-cloud) ## Setting up GitHub Enterprise Server permissions @@ -108,7 +108,7 @@ Assign GitHub Enterprise Server permissions for team members or collaborators to 1. Login to your GitHub Enterprise Server account. -2. Go to ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Profile** ➜ **Settings**. +2. Go to **Profile** ➜ **Settings**. 3. On your sidebar, click **Organizations**. @@ -179,7 +179,7 @@ The Git Integration for Jira app automatically configures web linking for GitHub 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](/git-integration-for-jira-cloud/web-linking/). +For more information on this feature, see [Documentation: Web linking](/git-integration-for-jira-cloud/web-linking-gij-cloud). ## Viewing git commits in Jira Cloud @@ -192,7 +192,7 @@ For more information on this feature, see [Documentation: Web linking](/git-inte 4. Click **View Full Commit** to view the code diff. -For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues/). +For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues-gij-cloud). ## Working with branches and pull requests with GitHub Enterprise Server @@ -222,14 +222,14 @@ On your Jira Cloud, open a Jira issue. On the Jira Git integration development p 3. Use the search box in the dropdown list to filter displayed repositories. - 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/User-Settings) page. + 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. -2. Choose a **Base branch**. OPTIONAL Designate the branch to be the default selected branch for the active repository. To configure default branches for more than one repository - use the [User settings](#) page. +2. Choose a **Base branch**. OPTIONAL Designate the branch to be the default selected branch for the active repository. To configure default branches for more than one repository - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. 3. Enter a **Branch name** or leave it as is (recommended). -For more detailed information on this feature, see [Create branch](/git-integration-for-jira-cloud/Create-branch). +For more detailed information on this feature, see [Create branch](/git-integration-for-jira-cloud/create-branch-gij-cloud). 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. @@ -249,9 +249,9 @@ The pull request feature works the same as merge request. On your Jira Cloud, op 3. Use the search box in the dropdown list to filter displayed repositories. - 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](#) page. + 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. -2. Choose the newly-created branch as the **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the active repository. To configure default branches for more than one repository - use the [User settings](#) page. +2. Choose the newly-created branch as the **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the active repository. To configure default branches for more than one repository - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. 3. Set _**master**_ as the **Target branch**. @@ -262,7 +262,7 @@ Pull/merge requests are still indexed based on branch name even if the PR/MR tit **Preview** allows you to see the comparison view of the current changes in the selected **Source branch** vs **Target branch** (_usually_ _master_). -For more detailed information on this feature, see [Create pull/merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request/). +For more detailed information on this feature, see [Create pull/merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud). The pull request is listed on the developer panel of the Jira issue page. diff --git a/git-integration-for-jira-cloud/github-webhook-events-gij-cloud.md b/git-integration-for-jira-cloud/github-webhook-events-gij-cloud.md index 07d58a0..a3cc730 100644 --- a/git-integration-for-jira-cloud/github-webhook-events-gij-cloud.md +++ b/git-integration-for-jira-cloud/github-webhook-events-gij-cloud.md @@ -9,25 +9,25 @@ taxonomy: --- The following are the supported types of GitHub events for triggering webhooks: -| | +### GitHub (Push Events) +| GitHub (Push Events) | | --- | -| ### GitHub (Push Events) | | _Type_
**pushEvents:** `"^push$"` | | _Request URI_
`/api/1/webhook/reindex/install/`****`/web` | | _Request headers_
**Content-type:** `application/x-www-form-urlencoded`
**X-GitHub-Event:** `push` | | _Request payload example_

```java
*{
...
"repository": {
"id": 224819315,
"git_url": "git://github.com/acme/test1.git",
"ssh_url": "git@github.com:acme/test1.git",
"clone_url": "https://github.com/acme/test1.git",
"svn_url": "https://github.com/acme/test1",
},
...
}
``` | -| | +### GitHub (Pull Request Events) +| GitHub (Pull Request Events) | | --- | -| ### GitHub (Pull Request Events) | | _Type_
**pullRequestEvents:** `"^pull_request$"` | | _Request URI_
`/api/1/webhook/reindex/install/`****`/web` | | _Request headers_
**Content-type:** `application/x-www-form-urlencoded`
**X-GitHub-Event:** `pull_request` | | _Request payload_

```java
*{
...
"repository": {
"id": 224819315,
"git_url": "git://github.com/acme/test1.git",
"ssh_url": "git@github.com:acme/test1.git",
"clone_url": "https://github.com/acme/test1.git",
"svn_url": "https://github.com/acme/test1",
},
...
}
``` | -| | -| --- | +### GitHub (Repository Events) | ### GitHub (Repository Events) | +| --- | | Type
**repositoryEvents:** "^repository$" | | _Request URI_
`/api/1/webhook/reindex/install/`****`/web` | | _Request headers_
**Content-Type:** `application/x-www-form-urlencoded`
**X-GitHub-Event:** `repository` | diff --git a/git-integration-for-jira-cloud/github-webhook-indexing-integration-gij-cloud.md b/git-integration-for-jira-cloud/github-webhook-indexing-integration-gij-cloud.md index 101f2c1..a615c76 100644 --- a/git-integration-for-jira-cloud/github-webhook-indexing-integration-gij-cloud.md +++ b/git-integration-for-jira-cloud/github-webhook-indexing-integration-gij-cloud.md @@ -8,22 +8,15 @@ taxonomy: --- For more information on Webhook indexing: -* [Webhook Indexing Explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer/) +* [Webhook Indexing Explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer-gij-cloud) -* [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud/) +* [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud) With the Webhook indexing integration, there is no need to enable indexing triggers in the git manager configuration page. For a step-by-step setup guide, watch the following demonstration videos: - -* [Setup webhook indexing integration (Repository Level)](#Repository-Level) - -* [Setup webhook indexing integration (Organization Level)](#Organization-Level) - - ## Video Guides - ### Repository Level _Right click_ [_**here**_](https://bigbrassband.wistia.com/medias/p54dj581ec) _and open this video in a new window/tab for more viewing options._ @@ -36,7 +29,7 @@ _Right click_ [_**here**_](https://bigbrassband.wistia.com/medias/l6msatuap5) _a The steps outlined below requires that [Git Integration for Jira](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=overview) app is already installed on your Jira Cloud instance. Otherwise, install the [Git Integration for Jira](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=overview) app first from the Atlassian Marketplace. -1. ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Webhook indexing integration** +1. **Webhook indexing integration** 1. On your Jira Cloud dashboard, go to **Apps** ➜ **Git Integration: Manage integrations**. @@ -59,16 +52,16 @@ The steps outlined below requires that [Git Integration for Jira](https://market ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1494646787/gitcloud-managed-ui-webhook-idx-github-setup(c).png?version=1&modificationDate=1648383893223&cacheVersion=1&api=v2) 1. The webhook indexing integration has been added to the manage integration list. - 2. ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Before clicking **Finish**, make sure to configure webhook for your git service. Use the **Webhook URL** and the **Secret key** then follow the steps below for repository level or organization level webhook setup. + 2. Before clicking **Finish**, make sure to configure webhook for your git service. Use the **Webhook URL** and the **Secret key** then follow the steps below for repository level or organization level webhook setup. -2. ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Repository Level** ([see full video walkthrough on this page](#Repository-Level)) +2. **Repository Level** ([see full video walkthrough on this page](#Repository-Level)) Open a new browser tab and login to your GitHub web portal to setup webhook triggers for the selected _**repository**_. Configure a webhook on your git service by performing the following steps: 1. On your GitHub web portal, open a repository to work on. 2. ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1494646787/github-webhooks-setup-add-loc(acc).png?version=1&modificationDate=1618548411025&cacheVersion=1&api=v2) - Go to ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Settings**. + Go to **Settings**. 3. On the sidebar, click **Webhooks**. @@ -94,13 +87,13 @@ The steps outlined below requires that [Git Integration for Jira](https://market 10. The webhook configuration is added to the webhooks list. -3. ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Organization Level** ([see full video walkthrough on this page](#Organization-Level)) +3. **Organization Level** ([see full video walkthrough on this page](#Organization-Level)) Open a new browser tab and login to your GitHub web portal to configure webhook triggers for your selected _**organization**_. Configure a webhook on your git service by performing the following steps: 1. On your GitHub web portal, open an organization to work on. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1494646787/github-web-acc-webhook-org-settings(c).png?version=1&modificationDate=1618478203844&cacheVersion=1&api=v2&width=612&height=461) - 2. Go to ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Settings**. The following screen is displayed. + 2. Go to **Settings**. The following screen is displayed. 3. ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1494646787/github-web-acc-webhook-org-add(ca).png?version=2&modificationDate=1618548809758&cacheVersion=1&api=v2) @@ -143,7 +136,7 @@ The events are detected only after the Webhook indexing integration. If you see Make a git commit if you don’t see any commits in the Git Commits tab of a Jira issue. -For information on this topic, see [Linking git commits, associating branches and pull requests to a Jira issue](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues/). +For information on this topic, see [Linking git commits, associating branches and pull requests to a Jira issue](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues-gij-cloud). ## Git Roll Up tab @@ -151,25 +144,25 @@ The Git Roll Up tab is now supported for GitHub webhook indexing integration. ## Limited features for GitHub webhook indexing integration -The feature table displays the supported git features for the selected git server. For more information, see [Feature matrix for Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud/). +The feature table displays the supported git features for the selected git server. For more information, see [Feature matrix for Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1494646787/gitcloud-webhook-indexing-compare-vs-full.png?version=1&modificationDate=1648550807671&cacheVersion=1&api=v2&width=566&height=372) ### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) Works with git servers behind firewall -The webhooks indexing integration limits the features available. However, networks hosting git do not need to be updated to allow incoming requests as long as outbound requests can be made. See [Webhook Indexing explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer/) for more information. +The webhooks indexing integration limits the features available. However, networks hosting git do not need to be updated to allow incoming requests as long as outbound requests can be made. See [Webhook Indexing explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer-gij-cloud) for more information. ### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) View commits, branches, pull requests in Jira -Commits, branches, pull requests are visible in the ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Jira Development Information** panel as well as in the ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Git Commits issue** tab and ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Git Integration** side panel of the Jira issue. Jira administrators can regulate access to these displays using the _View development tools_ permission. +Commits, branches, pull requests are visible in the **Jira Development Information** panel as well as in the **Git Commits issue** tab and **Git Integration** side panel of the Jira issue. Jira administrators can regulate access to these displays using the _View development tools_ permission. ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1494646787/gitcloud-jira-issue-webhook-idx-sample.png?version=1&modificationDate=1618483032016&cacheVersion=1&api=v2) -### ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) View tags in Jira +### View tags in Jira -COMMING SOON +COMING SOON -### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) Support for Automation for Jira + Smart Commits +### Support for Automation for Jira + Smart Commits **Automation for Jira** - the following triggers are supported: @@ -184,7 +177,7 @@ COMMING SOON 5. `Pull request merged` -**Smart Commits:** Atlassian’s Smart Commits are enabled by default. Additional Smart Commit commands are available. See [Smart Commits](/git-integration-for-jira-cloud/smart-commits-gij-cloud/) for more information. +**Smart Commits:** Atlassian’s Smart Commits are enabled by default. Additional Smart Commit commands are available. See [Smart Commits](/git-integration-for-jira-cloud/smart-commits-gij-cloud) for more information. ### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) Repository Browser @@ -197,15 +190,15 @@ The Repository Browser allows users to view commits in git repositories by branc ### ![(error)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/error.png) Create branches and pull requests in Jira -This feature is not supported with webhook indexing integration. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud/) +This feature is not supported with webhook indexing integration. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud) ### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) Support for large number of commits in git pushes -Git servers may truncate how much of the activity is captured in a webhook on large git push events resulting in some git activity. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud/). +Git servers may truncate how much of the activity is captured in a webhook on large git push events resulting in some git activity. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud). ### ![(error)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/error.png) Indexing full repository history -Webhook indexing integration will only show new commit/branch/pull request activity once webhooks are configured on the git server according to this wizard. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud/). +Webhook indexing integration will only show new commit/branch/pull request activity once webhooks are configured on the git server according to this wizard. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud). ### ![(error)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/error.png) View source code in Jira diff --git a/git-integration-for-jira-cloud/gitkraken-integration-settings-gij-cloud.md b/git-integration-for-jira-cloud/gitkraken-integration-settings-gij-cloud.md index 5ce20e3..4700f71 100644 --- a/git-integration-for-jira-cloud/gitkraken-integration-settings-gij-cloud.md +++ b/git-integration-for-jira-cloud/gitkraken-integration-settings-gij-cloud.md @@ -8,7 +8,7 @@ taxonomy: --- -This setting is part of the [**General settings**](/git-integration-for-jira-cloud/General-Settings) configuration page for Git Integration for Jira Cloud. +This setting is part of the [**General settings**](/git-integration-for-jira-cloud/general-settings-gij-cloud) configuration page for Git Integration for Jira Cloud. **Default settings** This setting is enabled in [**Git Integration for Jira Cloud**](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?tab=overview&hosting=cloud) app by default. @@ -24,7 +24,7 @@ Enable this setting to turn on the deep linking feature which allows you to quic The **View developer tools** _permission_ is required to view the git commits. Jira users must also have the **Browse Project** _permissions_ to a project associated with a repository to view. -For more details, see [Features: Deep Linking to the GitKraken Git client (Jira Cloud)](/git-integration-for-jira-cloud/deep-linking-to-the-gitkraken-client/). +For more details, see [Features: Deep Linking to the GitKraken Git client (Jira Cloud)](/git-integration-for-jira-cloud/deep-linking-to-the-gitkraken-client-gij-cloud). After all the settings have been configured according to your requirements, click **Update** to apply the changes. diff --git a/git-integration-for-jira-cloud/gitlab-ce-ee-eol-support-policy-gij-cloud.md b/git-integration-for-jira-cloud/gitlab-ce-ee-eol-support-policy-gij-cloud.md index ad3d36c..51b1a1a 100644 --- a/git-integration-for-jira-cloud/gitlab-ce-ee-eol-support-policy-gij-cloud.md +++ b/git-integration-for-jira-cloud/gitlab-ce-ee-eol-support-policy-gij-cloud.md @@ -23,4 +23,5 @@ These two policies are in place because: 5. Ensuring that tests pass on the older release is a considerable challenge in some cases, and as such is very time-consuming. -For more informaiton, see [GitLab releases](https://about.gitlab.com/releases/categories/releases/). \ No newline at end of file +For more informaiton, see [GitLab releases](https://about.gitlab.com/releases/categories/releases/). + diff --git a/git-integration-for-jira-cloud/gitlab-ce-ee-gij-cloud.md b/git-integration-for-jira-cloud/gitlab-ce-ee-gij-cloud.md index eae5067..d62da5b 100644 --- a/git-integration-for-jira-cloud/gitlab-ce-ee-gij-cloud.md +++ b/git-integration-for-jira-cloud/gitlab-ce-ee-gij-cloud.md @@ -6,7 +6,7 @@ taxonomy: category: git-integration-for-jira-cloud --- -Using **Jira Server or Data Center**? [See the corresponding article](/git-integration-for-jira-self-managed/gitlab-com-ce-ee/). +Using **Jira Server or Data Center**? [See the corresponding article](/git-integration-for-jira-self-managed/gitlab-ce-ee-gij-self-managed). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/85524528/image-20200815-134810.png?version=1&modificationDate=1597500982662&cacheVersion=1&api=v2&width=374&height=84) @@ -73,13 +73,13 @@ For more information, see [**GitLab Permissions »**](https://docs.gitlab.com/e If two-factor authentication is enabled for your GitLab Server account, you will need to create a personal access token (PAT) to access your git repositories. Enable two-factor authentication in your GitLab Server account for increased security. -While instructions from GitHub works just fine, [follow this article](/git-integration-for-jira-cloud/creating-personal-access-tokens/) for a quick step-by-step guide to get you started. +While instructions from GitHub works just fine, [follow this article](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud) for a quick step-by-step guide to get you started. ## Using Git service integration Support for Gitlab API v3 is deprecated. We recommend to use **GitLab API v4** when adding new integrations for increased security. -This process requires an existing GitLab Server EE or GitLab Server CE. If your GitLab Server version is 10.2 or newer, a [personal access token](/git-integration-for-jira-cloud/creating-personal-access-tokens/) must be configured. +This process requires an existing GitLab Server EE or GitLab Server CE. If your GitLab Server version is 10.2 or newer, a [personal access token](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud) must be configured. We recommend using the Full feature integrations panel to connect multiple repositories from your GitLab CE/EE account. @@ -102,12 +102,12 @@ We recommend using the Full feature integrations panel to connect multiple repos 2. Enter the **Host URL** of the GitLab Server - 3. Enter the **Personal Access Token** for server authentication. 2FA must be enabled in your GitLab Server and [PAT has been configured](/git-integration-for-jira-cloud/creating-personal-access-tokens/). + 3. Enter the **Personal Access Token** for server authentication. 2FA must be enabled in your GitLab Server and [PAT has been configured](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud). 4. Configuring the **Advanced** settings is optional. However, admins/power users may set how the project listing is displayed. These settings are used with integration to retrieve the list of tracked repositories. Set a filter that will only load some cloned repositories which can be viewed in the Manage repositories page. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/85524528/gitcloud-integration-advanced-options-wo-sslverify(c).png?version=1&modificationDate=1649688737208&cacheVersion=1&api=v2&width=533&height=279) - 1. **Custom API Path** – this 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. For more information on GitLab custom API paths, see [GitLab API](https://docs.gitlab.com/ee/api/projects.html). For more examples, see article [Jira Cloud: Working with Custom API Path](/wiki/spaces/GITCLOUD/pages/133201972/Working+with+Custom+API+Path). + 1. **Custom API Path** – this 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. For more information on GitLab custom API paths, see [GitLab API](https://docs.gitlab.com/ee/api/projects.html). For more examples, see article [Jira Cloud: Working with Custom API Path](/git-integration-for-jira-cloud/working-with-custom-api-path-gij-cloud). ```java GitLab version API support: @@ -117,7 +117,7 @@ We recommend using the Full feature integrations panel to connect multiple repos 2. **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. Read about JMESPath expressions on their [website](http://jmespath.org/). For help with writing expressions, please contact [support](mailto:support@bigbrassband.com). - To know more examples, see article [Jira Cloud: Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters/). + To know more examples, see article [Jira Cloud: Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud). 5. While Custom API Path and JMESPath filter are mutually exclusive, you can use one, the other, both or neither. @@ -141,7 +141,7 @@ The Git Integration for Jira app supports GitLab API v4 (in both Jira Cloud and For newer GitLab authentication - in order to access a Git repository over HTTP, use the username as the username and the PAT for the password. **Administrators** -If you need to require users PAT for creating branches or merge requests, turn on this setting via the selected integration in Manage integrations page ➜ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Actions ➜ **Edit integration**. +If you need to require users PAT for creating branches or merge requests, turn on this setting via the selected integration in Manage integrations page ➜ Actions ➜ **Edit integration**. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/85524528/gitcloud-edit-integration-feature-cfg-req-user-PAT.png?version=1&modificationDate=1649690453368&cacheVersion=1&api=v2&width=680&height=75) @@ -151,9 +151,9 @@ This process requires an existing GitLab CE/EE git repository. Look for the the Use this information to connect the GitLab CE/EE git repository to your Jira Cloud via Git Integration for Jira app: -[Single git repository integration (HTTPS)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-http-https/) +[Single git repository integration (HTTPS)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-http-https-gij-cloud) -[Single git repository integration (SSH)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-ssh/) +[Single git repository integration (SSH)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-ssh-gij-cloud) There will be a slight delay in adding 2FA-enabled repositories compared to others. These will show in the git configuration list eventually. @@ -165,7 +165,7 @@ The Git Integration for Jira app automatically configures web linking for GitLab 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](/git-integration-for-jira-cloud/web-linking/). +For more information on this feature, see [Documentation: Web linking](/git-integration-for-jira-cloud/web-linking-gij-cloud). ## Viewing git commits in Jira Cloud @@ -178,7 +178,7 @@ For more information on this feature, see [Documentation: Web linking](/git-inte 4. Click **View Full Commit** to view the code diff. -For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues/). +For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues-gij-cloud). ## Working with branches and merge requests with GitLab CE/EE @@ -192,7 +192,7 @@ Main branch for repositories within an integration can only be changed on the gi ### Creating Branches -On your Jira Cloud, open a Jira issue. On the [Jira Git integration development panel](/git-integration-for-jira-cloud/jira-git-integration-development-panel/), click **Open Git Integration** then click **Create branch**. The following dialog is displayed. +On your Jira Cloud, open a Jira issue. On the [Jira Git integration development panel](/git-integration-for-jira-cloud/jira-git-integration-development-panel-gij-cloud), click **Open Git Integration** then click **Create branch**. The following dialog is displayed. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/85524528/gitcloud-gitlab-ceee-create-branch-dlg.png?version=1&modificationDate=1649691446984&cacheVersion=1&api=v2&width=680&height=221) @@ -206,16 +206,16 @@ On your Jira Cloud, open a Jira issue. On the [Jira Git integration development 3. Use the search box in the dropdown list to filter displayed repositories. - 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/user-settings/) page. + 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. -2. Choose a **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one connected repository - use the [User settings](/git-integration-for-jira-cloud/gitlab-com/) page. +2. Choose a **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one connected repository - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. 3. Enter a **Branch name** or leave it as is (recommended). 4. Click **Create branch** to complete this process. -For more detailed information on this feature, see [Create Branch](/git-integration-for-jira-cloud/Create-branch). +For more detailed information on this feature, see [Create Branch](/git-integration-for-jira-cloud/create-branch-gij-cloud). 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. @@ -236,9 +236,9 @@ The merge request feature works the same as merge request. On your Jira Cloud, o 3. Use the search box in the dropdown list to filter displayed repositories. - 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/gitlab-com/) page. + 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/gitlab-com-gij-cloud) page. -2. Choose the newly-created branch as the **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one connected repository - use the [User settings](/git-integration-for-jira-cloud/gitlab-com/) page. +2. Choose the newly-created branch as the **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one connected repository - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. 3. Set _**master**_ as the **Target branch**. @@ -251,7 +251,7 @@ Merge requests are still indexed based on branch name even if the MR title does **Preview** allows you to see the comparison view of the current changes in the selected **Source branch** vs **Target branch** (_usually_ _master_). -For more detailed information on this feature, see [Creating merge requests](/git-integration-for-jira-cloud/create-pull-or-merge-request/). +For more detailed information on this feature, see [Creating merge requests](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud) The merge request is listed on the developer panel of the Jira issue page. diff --git a/git-integration-for-jira-cloud/gitlab-com-gij-cloud.md b/git-integration-for-jira-cloud/gitlab-com-gij-cloud.md index 2e84793..9b1b26c 100644 --- a/git-integration-for-jira-cloud/gitlab-com-gij-cloud.md +++ b/git-integration-for-jira-cloud/gitlab-com-gij-cloud.md @@ -6,7 +6,7 @@ taxonomy: category: git-integration-for-jira-cloud --- -Using **Jira Server or Data Center**? [See the corresponding article](https://bigbrassband.atlassian.net/wiki/x/iABMAw). +Using **Jira Server or Data Center**? [See the corresponding article](/git-integration-for-jira-self-managed/gitlab-gij-self-managed). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/85622895/gitlab_wm_no_bg.png?version=1&modificationDate=1597499071261&cacheVersion=1&api=v2&width=224&height=84) @@ -67,7 +67,7 @@ For more information, see [**GitLab Permissions »**](https://docs.gitlab.com/e If two-factor authentication is enabled for your GitLab account, you will need to create a personal access token (PAT) to access your git repositories. Enable two-factor authentication in your GitLab.com account for increased security. -While instructions from GitHub works just fine, [follow this article](http://bigbrassband.atlassian.net/wiki/spaces/GITCLOUD/pages/107216897/Creating+Personal+Access+Tokens#CreatingPersonalAccessTokens-gitlab) for a quick step-by-step guide to get you started. +While instructions from GitHub works just fine, [follow this article](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud) for a quick step-by-step guide to get you started. ## Using Git service integration @@ -101,7 +101,7 @@ We recommend using the Git service integration panel[1](#logo) to connect multip ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/85622895/gitcloud-integration-advanced-options-wo-sslverify(c).png?version=1&modificationDate=1649327432387&cacheVersion=1&api=v2&width=533&height=279) * **Custom API Path** – this 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. For more information on GitLab custom API paths, see [GitLab API](https://docs.gitlab.com/ee/api/projects.html). - For more examples, see article [Jira Cloud: Working with Custom API Path](http://bigbrassband.atlassian.net/wiki/spaces/GITCLOUD/pages/133201972/Working+with+Custom+API+Path). + For more examples, see article [Jira Cloud: Working with Custom API Path](/git-integration-for-jira-cloud/working-with-custom-api-path-gij-cloud). ```java GitLab version API support: @@ -117,7 +117,7 @@ We recommend using the Git service integration panel[1](#logo) to connect multip * **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. Read about JMESPath expressions on their [website](http://jmespath.org/). For help with writing expressions, please contact [support](mailto:support@bigbrassband.com). - To learn more examples, see article [Jira Cloud: Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters/). + To learn more examples, see article [Jira Cloud: Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud). 4. While Custom API Path and JMESPath filter are mutually exclusive, you can use one, the other, both or neither. @@ -140,7 +140,7 @@ The GitLab.com git repositories are now connected to Jira Cloud. There will be a slight delay in adding 2FA-enabled repositories compared to others. These will show in the git configuration list eventually. **Administrators** -If you need to require users PAT for creating branches or merge requests, turn on this setting via the selected integration in Manage integrations page ➜ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Actions ➜ **Edit integration** ➜ Feature settings. +If you need to require users PAT for creating branches or merge requests, turn on this setting via the selected integration in Manage integrations page ➜ Actions ➜ **Edit integration** ➜ Feature settings. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/85622895/gitcloud-edit-integration-feature-cfg-req-user-PAT.png?version=1&modificationDate=1649328090252&cacheVersion=1&api=v2&width=680&height=75) @@ -150,9 +150,9 @@ This process requires an existing GitLab git repository. Look for the the GitLa Use this information to connect the GitLab git repository to your Jira Cloud via Git Integration for Jira app: -[Single git repository integration (HTTPS)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-http-https/) +[Single git repository integration (HTTPS)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-http-https-gij-cloud) -[Single git repository integration (SSH)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-ssh/) +[Single git repository integration (SSH)](/git-integration-for-jira-cloud/connecting-to-a-single-git-repository-ssh-gij-cloud) There will be a slight delay in adding 2FA-enabled repositories compared to others. These will show in the git configuration list eventually. @@ -164,7 +164,7 @@ The Git Integration for Jira app automatically configures web linking for GitLab 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](/git-integration-for-jira-cloud/web-linking/). +For more information on this feature, see [Documentation: Web linking](/git-integration-for-jira-cloud/web-linking-gij-cloud). ## Viewing git commits in Jira Cloud @@ -177,7 +177,7 @@ For more information on this feature, see [Documentation: Web linking](/git-inte 4. Click **View full commit** to view the code diff. -For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues/). +For more information about this feature, see [Documentation: Linking git commits to Jira issues](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues-gij-cloud). ## Working with branches and merge requests with GitLab @@ -207,16 +207,16 @@ On your Jira Cloud instance, open a Jira issue. On the Jira Git integration deve 3. Use the search box in the dropdown list to filter displayed repositories. - 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/User-Settings) page. + 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. -2. Choose a **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one connected repository - use the [User settings](#) page. +2. Choose a **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one connected repository - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. 3. Enter a **Branch name** or leave it as is (recommended). 4. Click **Create branch** to complete this process. -For more detailed information on this feature, see [Create branch](/git-integration-for-jira-cloud/Create-branch). +For more detailed information on this feature, see [Create branch](/git-integration-for-jira-cloud/create-branch-gij-cloud). 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. @@ -239,7 +239,7 @@ The merge request feature works the same as merge request. On your Jira Cloud, o 4. OPTIONAL Designate the repository to be the default selected repository for current Jira project. To configure default repositories for more than one Jira project - use the [User settings](#) page. -2. Choose the newly-created branch as the **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one connected repository - use the [User settings](#) page. +2. Choose the newly-created branch as the **Source branch**. OPTIONAL Designate the branch to be the default selected branch for the currently selected repository. To configure default branches for more than one connected repository - use the [User settings](/git-integration-for-jira-cloud/user-settings-gij-cloud) page. 3. Set _**master**_ as the **Target branch**. @@ -252,7 +252,7 @@ Merge requests are still indexed based on branch name even if the MR title does **Preview** allows you to see the comparison view of the current changes in the selected **Source branch** vs **Target branch** (_usually_ _master_). -For more detailed information on this feature, see [Create pull/merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request/). +For more detailed information on this feature, see [Create pull/merge request](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud). The merge request is listed on the developer panel of the Jira issue page. diff --git a/git-integration-for-jira-cloud/gitlab-com-gitlab-ce-ee-jmespath-filter-examples-gij-cloud.md b/git-integration-for-jira-cloud/gitlab-com-gitlab-ce-ee-jmespath-filter-examples-gij-cloud.md index 54e1510..be12d63 100644 --- a/git-integration-for-jira-cloud/gitlab-com-gitlab-ce-ee-jmespath-filter-examples-gij-cloud.md +++ b/git-integration-for-jira-cloud/gitlab-com-gitlab-ce-ee-jmespath-filter-examples-gij-cloud.md @@ -10,35 +10,30 @@ taxonomy: An optional JMESPath filter can be configured when adding GitLab integration or repositories. -| | -| --- | | **1\. Contains (include)** | +| --- | | ```java
[?contains(name, 'git') \| contains(name, 'Slap') \| contains(name, 'est')]
``` | | This is a filter based on text in the repository name. It will list all the repositories that contain the specified names. Do note that the declared string format is case-sensitive. | -| | -| --- | | **2\. Contains (exclude)** | +| --- | | ```java
[?(!contains(tag_list, 'largemedia'))]
[?(!contains(name, 'firstword'))]
[?(!contains(name, 'firstword')) \| (!contains(name, 'secondword'))]
``` | | 1 – Blacklists project tag.
2 – Lists repositories with names that either do not contain the word `'firstword'`.
3 – Lists repositories with names that either do not contain the words `‘firstword’` OR `‘secondword’`. | | The `!condition` must be wrapped in a parenthesis so it won’t invert the whole expression. | -| | -| --- | | **3\. Tags** | +| --- | | ```java
[?contains(tag_list, 'largemedia')]
``` | | Whitelists project tag. | | **Note:**
GitLab refers to _**project tags**_ as tags in the API and in some places in the UI but the actual setting is called **Topics**. | -| | -| --- | | **4\. Starts with or ends with** | +| --- | | ```java
[?starts_with(name, 'git') \| ends_with(name, 'test')]
``` | | Lists repositories with names that starts with `'git'` or ends with `'test'`. | -| | -| --- | | **5\. Exclude projects without repositories** | +| --- | | ```java
[?!empty_repo]
``` | | Lists only repositories from projects that have existing repositories. | diff --git a/git-integration-for-jira-cloud/gitlab-webhook-events-gij-cloud.md b/git-integration-for-jira-cloud/gitlab-webhook-events-gij-cloud.md index 59db024..ee061cd 100644 --- a/git-integration-for-jira-cloud/gitlab-webhook-events-gij-cloud.md +++ b/git-integration-for-jira-cloud/gitlab-webhook-events-gij-cloud.md @@ -37,3 +37,4 @@ _Request URI_
/api/1/webhook/reindex/install/****/web _Request headers_
**Content-type:** `application/json`
**X-GitHub-Event:** `system hook` _Request payload example_

```java
{
"owner_email": "admin@example.com",
"path": "jsmith_4",
"owner_name": "Administrator",
"project_id": 85,
"path_with_namespace": "root/jsmith_4",
"name": "JohnSmith_5",
"project_visibility": "private",
"event_name": "project_destroy",
}
``` + diff --git a/git-integration-for-jira-cloud/gitlab-webhook-indexing-integration-gij-cloud.md b/git-integration-for-jira-cloud/gitlab-webhook-indexing-integration-gij-cloud.md index 298128a..f9a7fbe 100644 --- a/git-integration-for-jira-cloud/gitlab-webhook-indexing-integration-gij-cloud.md +++ b/git-integration-for-jira-cloud/gitlab-webhook-indexing-integration-gij-cloud.md @@ -8,22 +8,22 @@ taxonomy: --- For more information on Webhook indexing: -* [Webhook Indexing Explainer](/git-integration-for-jira-cloud/webhook-indexing-integration/) +* [Webhook Indexing Explainer](/git-integration-for-jira-cloud/webhook-indexing-integration-gij-cloud) -* [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud/) +* [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/features-gij-cloud) With webhook indexing integration, there’s no need to enable indexing triggers in the git manager configuration page. + +## Video Guides + For a step-by-step setup guide, watch the following demonstration videos: * [Setup webhook indexing integration (Repository Level)](#Repository-Level) * [Setup webhook indexing integration (Group Level)](#Group-Level) - -## Video Guides - ### Repository Level _Right click_ [_**here**_](https://bigbrassband.wistia.com/medias/ejgouua9x4) _and open this video in a new window/tab for more viewing options._ @@ -36,7 +36,7 @@ _Right click_ [_**here**_](https://bigbrassband.wistia.com/medias/uh616awfnj) _a The steps outlined below requires that [Git Integration for Jira](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=overview) app is already installed on your Jira Cloud instance. Otherwise, install the [Git Integration for Jira](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=overview) app first from the Atlassian Marketplace. -1. ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Webhook indexing integration** +1. **Webhook indexing integration** 1. On your Jira Cloud dashboard, go to **Apps** ➜ **Git Integration: Manage integrations**. @@ -57,14 +57,14 @@ The steps outlined below requires that [Git Integration for Jira](https://market ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1503494176/gitcloud-managed-ui-webhook-idx-gitlab-setup(c).png?version=1&modificationDate=1648551862902&cacheVersion=1&api=v2) 1. Enter webhook indexing integration has been added to the manage integration list. - 2. ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Before clicking **Finish**, make sure to configure webhook for your git service. Use the **Webhook URL** and the **Secret key** then follow the steps below for repository level or organization level webhook setup. + 2. Before clicking **Finish**, make sure to configure webhook for your git service. Use the **Webhook URL** and the **Secret key** then follow the steps below for repository level or organization level webhook setup. -2. ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) REPOSITORY LEVEL **GitLab Repository webhook setup** (see full video walkthrough on this page) +2. REPOSITORY LEVEL **GitLab Repository webhook setup** (see full video walkthrough on this page) Open a new browser tab and login to your GitLab web portal to setup webhook triggers for the selected _**repository**_. Configure a webhook on your git service by performing the following steps: 1. On your GitLab web portal, open a repository to work on. - 2. Go to ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Settings**. + 2. Go to **Settings**. 3. ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1503494176/gitlab-web-repo-portal-sample(c).png?version=1&modificationDate=1618662448010&cacheVersion=1&api=v2) @@ -90,12 +90,12 @@ The steps outlined below requires that [Git Integration for Jira](https://market 9. The webhook configuration is added to the webhooks list. -3. ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) GROUP LEVEL **GitLab Group webhook setup** (see full video walkthrough on this page) +3. GROUP LEVEL **GitLab Group webhook setup** (see full video walkthrough on this page) Open a new browser tab and login to your GitLab web portal to setup webhook triggers for the selected _**group**_. Configure a webhook on your git service by performing the following steps: 1. On your GitLab web portal, go to **Your groups** and open a group to work on. - 2. Go to ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Settings**. + 2. Go to **Settings**. 3. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1503494176/gitlab-group-setup-webhooks-01(c).png?version=1&modificationDate=1621094785971&cacheVersion=1&api=v2&width=612&height=419) @@ -132,7 +132,7 @@ Edit integration settings via **Actions** on the Manage Git repository page. In Make a commit if you don’t see commits in the Git Commits tab of an associated Jira issue. -For information on this topic, see [Linking git commits, associating branches and pull requests to a Jira issue](/wiki/spaces/GITCLOUD/pages/1503526923). +For information on this topic, see [Linking git commits, associating branches and pull requests to a Jira issue](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues-gij-cloud). ## Git Roll Up tab @@ -140,23 +140,23 @@ The Git Roll Up tab is now supported for GitLab webhook indexing integration. ## Limited features for GitLab webhook indexing integration -The feature table displays the supported git features for the selected git server. For more information, see [Feature matrix for Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud/). +The feature table displays the supported git features for the selected git server. For more information, see [Feature matrix for Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1503494176/gitcloud-webhook-indexing-compare-vs-full-gitlab.png?version=1&modificationDate=1648552846840&cacheVersion=1&api=v2&width=566&height=372) ### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) Works with git servers behind firewall -The webhooks indexing integration limits the features available. However, networks hosting git do not need to be updated to allow incoming requests as long as outbound requests can be made. See [Webhook Indexing explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer/) for more information. +The webhooks indexing integration limits the features available. However, networks hosting git do not need to be updated to allow incoming requests as long as outbound requests can be made. See [Webhook Indexing explainer](/git-integration-for-jira-cloud/webhook-indexing-explainer-gij-cloud) for more information. ### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) View commits, branches, pull requests in Jira -Commits, branches, pull requests are visible in the ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Jira Development Information** panel as well as in the ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Git Commits issue** tab and ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) **Git Integration** side panel of the Jira issue. Jira administrators can regulate access to these displays using the _View development tools_ permission. +Commits, branches, pull requests are visible in the**Jira Development Information** panel as well as in the **Git Commits issue** tab and **Git Integration** side panel of the Jira issue. Jira administrators can regulate access to these displays using the _View development tools_ permission. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1503494176/gitcloud-jira-issue-webhook-idx-gitlab.png?version=2&modificationDate=1618832120050&cacheVersion=1&api=v2&width=680&height=369) -### ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) View tags in Jira +### View tags in Jira -COMMING SOON +COMING SOON ### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) Support for Automation for Jira + Smart Commits @@ -173,7 +173,7 @@ COMMING SOON 5. `Pull request merged` -**Smart Commits:** Atlassian’s Smart Commits are enabled by default. Additional Smart Commit commands are available. See [Smart Commits](https://bigbrassband.com/git-integration-for-jira/documentation/smart-commits.html) for more information. +**Smart Commits:** Atlassian’s Smart Commits are enabled by default. Additional Smart Commit commands are available. See [Smart Commits](/git-integration-for-jira-cloud/smart-commits-gij-cloud) for more information. ### ![(tick)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/check.png) Repository Browser @@ -186,15 +186,15 @@ The Repository Browser allows users to view commits in git repositories by branc ### ![(error)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/error.png) Create branches and pull requests in Jira -This feature is not supported with webhook indexing integration. For more information, see [Feature matrix of Git Integration for Jira Cloud](/wiki/spaces/GITCLOUD/pages/1470398499/Feature+matrix+of+Git+Integration+for+Jira+Cloud) +This feature is not supported with webhook indexing integration. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud) -### ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Support for large number of commits in git pushes +### Support for large number of commits in git pushes -Git servers may truncate how much of the activity is captured in a webhook on large git push events resulting in some git activity. For more information, see [Feature matrix of Git Integration for Jira Cloud](/wiki/spaces/GITCLOUD/pages/1470398499/Feature+matrix+of+Git+Integration+for+Jira+Cloud). +Git servers may truncate how much of the activity is captured in a webhook on large git push events resulting in some git activity. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud). ### ![(error)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/error.png) Indexing full repository history -Webhook indexing integration will only show new commit/branch/pull request activity once webhooks are configured on the git server according to this wizard. For more information, see [Feature matrix of Git Integration for Jira Cloud](/wiki/spaces/GITCLOUD/pages/1470398499/Feature+matrix+of+Git+Integration+for+Jira+Cloud). +Webhook indexing integration will only show new commit/branch/pull request activity once webhooks are configured on the git server according to this wizard. For more information, see [Feature matrix of Git Integration for Jira Cloud](/git-integration-for-jira-cloud/feature-matrix-of-git-integration-for-jira-cloud-gij-cloud). ### ![(error)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/error.png) View source code in Jira diff --git a/git-integration-for-jira-cloud/glossary-of-terms-gij-cloud.md b/git-integration-for-jira-cloud/glossary-of-terms-gij-cloud.md index 5a5d4f5..9956c02 100644 --- a/git-integration-for-jira-cloud/glossary-of-terms-gij-cloud.md +++ b/git-integration-for-jira-cloud/glossary-of-terms-gij-cloud.md @@ -44,6 +44,6 @@ Lucene is an index service within your Jira instance. It ships with Jira and Git This database stores information about all commits _(comment, author, etc)_ as well as the branch name which the commit belongs to. -[« Localization support](/git-integration-for-jira-cloud/localization-support-gij-cloud/) +[« Localization support](/git-integration-for-jira-cloud/localization-support-gij-cloud) -[Licensing notice »](/git-integration-for-jira-cloud/Licensing-notice) \ No newline at end of file +[Licensing notice »](/git-integration-for-jira-cloud/licensing-notice-gij-cloud) \ No newline at end of file diff --git a/git-integration-for-jira-cloud/hooks-and-webhooks-gij-cloud.md b/git-integration-for-jira-cloud/hooks-and-webhooks-gij-cloud.md index 2421bb1..72b9611 100644 --- a/git-integration-for-jira-cloud/hooks-and-webhooks-gij-cloud.md +++ b/git-integration-for-jira-cloud/hooks-and-webhooks-gij-cloud.md @@ -24,18 +24,18 @@ On this page, you will find the list of available hooks and webhooks supported b -[Client-side Hook](/git-integration-for-jira-cloud/commit-msg-hook/) +[Client-side Hook](/git-integration-for-jira-cloud/commit-msg-hook-gij-cloud) The **_commit-msg_** hook is a python script file that must be located in the developer's local repository. -[Server-side Hook](/git-integration-for-jira-cloud/server-side-hook/) +[Server-side Hook](/git-integration-for-jira-cloud/server-side-hook-gij-cloud) Use server-side hooks to apply policies for your project. The server runs these scripts before and after the push. The server-side hook, like commit-msg hook, requires Python to be installed. -[Indexing Triggers](/git-integration-for-jira-cloud/Indexing-Triggers) +[Indexing Triggers](/git-integration-for-jira-cloud/indexing-triggers-gij-cloud) Trigger immediate reindex of your repositories from remote systems via webhooks. \ No newline at end of file diff --git a/git-integration-for-jira-cloud/how-can-a-jira-administrator-enable-or-disable-jira-development-information-gij-cloud.md b/git-integration-for-jira-cloud/how-can-a-jira-administrator-enable-or-disable-jira-development-information-gij-cloud.md index e79e050..4cd599f 100644 --- a/git-integration-for-jira-cloud/how-can-a-jira-administrator-enable-or-disable-jira-development-information-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-can-a-jira-administrator-enable-or-disable-jira-development-information-gij-cloud.md @@ -8,7 +8,7 @@ taxonomy: --- Install the [**Git Integration for Jira**](https://marketplace.atlassian.com/4984) or the [**Dev Info for Jira**](https://marketplace.atlassian.com/1219270) app. -1. Navigate to the **General settings** page of the application (![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) _Jira Settings_ ➜ _Apps_ ➜ _(sidebar) General settings_). +1. Navigate to the **General settings** page of the application _Jira Settings_ ➜ _Apps_ ➜ _(sidebar) General settings_). 2. Enable or disable the setting: **Send Development Information to Jira Cloud**. diff --git a/git-integration-for-jira-cloud/how-can-a-jira-administrator-enable-or-disable-the-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-gij-cloud.md b/git-integration-for-jira-cloud/how-can-a-jira-administrator-enable-or-disable-the-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-gij-cloud.md index fc143ee..28c8514 100644 --- a/git-integration-for-jira-cloud/how-can-a-jira-administrator-enable-or-disable-the-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-can-a-jira-administrator-enable-or-disable-the-jira-cloud-smart-commits-automation-for-jira-and-workflow-triggers-gij-cloud.md @@ -9,7 +9,7 @@ taxonomy: 1. Install the [**Git Integration for Jira**](https://marketplace.atlassian.com/4984) or the [**Dev Info for Jira**](https://marketplace.atlassian.com/1219270) app. -2. Navigate to the **General settings** page of the application (![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) _Jira Settings_ ➜ _Apps_ ➜ (sidebar) _General settings_). +2. Navigate to the **General settings** page of the application _Jira Settings_ ➜ _Apps_ ➜ (sidebar) _General settings_). 3. Click the **Send Development Information to Jira Cloud** checkbox to mark and enable it. This also allows access to the **Enable Jira Cloud Smart Commits, Automation for Jira and Workflow Triggers** setting. @@ -22,8 +22,7 @@ taxonomy: [**More information from Atlassian**](https://confluence.atlassian.com/jirasoftwarecloud/configuring-development-tools-764478056.html#Configuringdevelopmenttools-Workflowtriggers) -| | -| --- | | **Administrator note** | +| --- | | Both **Send Development Information to Jira Cloud** and **Enable Dev Info Smart Commits & Workflow** settings must be enabled for automatic workflow triggers to be enabled.

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1940914229/gitcloud-general-settings.png%3Fversion=1&modificationDate=1561755642353&cacheVersion=1&api=v2&width=350&height=184?version=1&modificationDate=1631336816979&cacheVersion=1&api=v2&width=442&height=232) | diff --git a/git-integration-for-jira-cloud/how-do-i-determine-the-git-integration-for-jira-app-pricing-after-the-trial-gij-cloud.md b/git-integration-for-jira-cloud/how-do-i-determine-the-git-integration-for-jira-app-pricing-after-the-trial-gij-cloud.md index 0028d35..eb9ab9d 100644 --- a/git-integration-for-jira-cloud/how-do-i-determine-the-git-integration-for-jira-app-pricing-after-the-trial-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-do-i-determine-the-git-integration-for-jira-app-pricing-after-the-trial-gij-cloud.md @@ -33,5 +33,4 @@ There are four ways to determine the pricing: Select the **Quote** option then **Deployment** (Server/Cloud/DC) and follow the instructions. -All four should provide the same answer. - +All four should provide the same answer. \ No newline at end of file diff --git a/git-integration-for-jira-cloud/how-to-articles-gij-cloud.md b/git-integration-for-jira-cloud/how-to-articles-gij-cloud.md index d5d9f15..06e0249 100644 --- a/git-integration-for-jira-cloud/how-to-articles-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-to-articles-gij-cloud.md @@ -11,18 +11,28 @@ Add how-to article * * * -| Title | Creator | Modified | -| --- | --- | --- | -| [Creating Personal Access Tokens](/wiki/spaces/GITCLOUD/pages/107216897/Creating+Personal+Access+Tokens) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Apr 25, 2022 | -| [Connecting SSH Git Repositories to Jira Cloud](/wiki/spaces/GITCLOUD/pages/864288769/Connecting+SSH+Git+Repositories+to+Jira+Cloud) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Apr 17, 2022 | -| [How to link pull or merge requests to a Jira issue?](/wiki/spaces/GITCLOUD/pages/2091220997) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Mar 18, 2022 | -| [How to link branches to a Jira issue?](/wiki/spaces/GITCLOUD/pages/2090729485) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Mar 18, 2022 | -| [How to link commits, branches and pull requests to a Jira issue?](/wiki/spaces/GITCLOUD/pages/1503526923) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Mar 18, 2022 | -| [Allow list (whitelist) BigBrassBand Cloud](/wiki/spaces/GITCLOUD/pages/121241614/Allow+list+%28whitelist%29+BigBrassBand+Cloud) | [Adam Wride](/people/557058:722bff1a-09a0-4ddd-b711-f23d9b67d17a?ref=confluence) | Mar 17, 2022 | -| [Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters/) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Dec 02, 2021 | -| [Working with Custom API Path](/wiki/spaces/GITCLOUD/pages/133201972/Working+with+Custom+API+Path) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Dec 01, 2021 | -| [How to get a quote?](/wiki/spaces/GITCLOUD/pages/1165459457) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Feb 05, 2021 | -| [Require Personal Access Tokens for user actions (create branch/pull request)](/wiki/spaces/GITCLOUD/pages/131137621) | [Adam Wride](/people/557058:722bff1a-09a0-4ddd-b711-f23d9b67d17a?ref=confluence) | Sep 07, 2020 | -| [Setting Project Permissions](/wiki/spaces/GITCLOUD/pages/509509708/Setting+Project+Permissions) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | May 21, 2020 | -| [How to Create Reindex Triggers for a Single Repository](/wiki/spaces/GITCLOUD/pages/132448361/How+to+Create+Reindex+Triggers+for+a+Single+Repository) | [Shanmarc Florete](/people/557058:1e48e57d-18d4-4bf2-8ae7-0e8b25958331?ref=confluence) | Sep 14, 2019 | -| [How to Calculate Pricing](/wiki/spaces/GITCLOUD/pages/128483369/How+to+Calculate+Pricing) | [Adam Wride](/people/557058:722bff1a-09a0-4ddd-b711-f23d9b67d17a?ref=confluence) | May 10, 2019 | \ No newline at end of file +[Creating Personal Access Tokens](/git-integration-for-jira-cloud/creating-personal-access-tokens-gij-cloud) + +[Connecting SSH Git Repositories to Jira Cloud](/git-integration-for-jira-cloud/connecting-ssh-git-repositories-to-jira-cloud-gij-cloud) + +[How to link pull or merge requests to a Jira issue?](/git-integration-for-jira-cloud/how-to-link-pull-or-merge-requests-to-a-jira-issue-gij-cloud) + +[How to link branches to a Jira issue?](/git-integration-for-jira-cloud/how-to-link-branches-to-a-jira-issue-gij-cloud) + +[How to link commits, branches and pull requests to a Jira issue?](/git-integration-for-jira-cloud/how-to-link-commits-branches-and-pull-requests-to-a-jira-issue-gij-cloud) + +[Allow list (whitelist) BigBrassBand Cloud](/git-integration-for-jira-cloud/allow-list-whitelist-bigbrassband-cloud-gij-cloud) + +[Working with JMESPath Filters](/git-integration-for-jira-cloud/working-with-jmespath-filters-gij-cloud) + +[Working with Custom API Path](/git-integration-for-jira-cloud/working-with-custom-api-path-gij-cloud) + +[How to get a quote?](/git-integration-for-jira-cloud/how-to-get-a-quote-gij-cloud) + +[Require Personal Access Tokens for user actions (create branch/pull request)](/git-integration-for-jira-cloud/require-personal-access-tokens-for-user-actions-create-branch-pull-request-gij-cloud) + +[Setting Project Permissions](/git-integration-for-jira-cloud/setting-project-permissions-gij-cloud) + +[How to Create Reindex Triggers for a Single Repository](/git-integration-for-jira-cloud/how-to-create-reindex-%20triggers-for-a-single-repository-gij-cloud) + +[How to Calculate Pricing](/git-integration-for-jira-cloud/how-to-calculate-pricing-gij-cloud) \ No newline at end of file diff --git a/git-integration-for-jira-cloud/how-to-calculate-pricing-gij-cloud.md b/git-integration-for-jira-cloud/how-to-calculate-pricing-gij-cloud.md index 875a6b7..f3bb00a 100644 --- a/git-integration-for-jira-cloud/how-to-calculate-pricing-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-to-calculate-pricing-gij-cloud.md @@ -12,10 +12,9 @@ taxonomy: 1. Use the [Atlassian Cloud Pricing Calculator](https://www.atlassian.com/software/pricing-calculator). First choose between **monthly/annual**, enter the **\# of seats** your Jira is licensed for, select **Apps**, select **Git Integration for Jira (Top Selling)** from the list of dropdowns. 2. See pricing details on the [Atlassian Marketplace: Git Integration for Jira](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=pricing) -3. Install the [Git Integration for Jira](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=pricing) then go to `[https://replacewithyourJiraname.atlassian.net/admin/billing/estimate](https://replacewithyourJiraname.atlassian.net/admin/billing/estimate)`. The estimated monthly or annual price will be quoted. +3. Install the [Git Integration for Jira](https://marketplace.atlassian.com/apps/4984/git-integration-for-jira?hosting=cloud&tab=pricing) then go to [https://replacewithyourJiraname.atlassian.net/admin/billing/estimate](https://replacewithyourJiraname.atlassian.net/admin/billing/estimate). The estimated monthly or annual price will be quoted. 4. [Contact Atlassian](https://www.atlassian.com/company/contact/purchasing-licensing) to create a quote. You can expect an answer within a business day. All active Jira users must be licensed for an Atlassian Marketplace app - [Atlassian Marketplace FAQ](https://www.atlassian.com/licensing/marketplace#licensingandpricing-1) - diff --git a/git-integration-for-jira-cloud/how-to-create-reindex- triggers-for-a-single-repository-gij-cloud.md b/git-integration-for-jira-cloud/how-to-create-reindex- triggers-for-a-single-repository-gij-cloud.md index 0427ccd..ec53a70 100644 --- a/git-integration-for-jira-cloud/how-to-create-reindex- triggers-for-a-single-repository-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-to-create-reindex- triggers-for-a-single-repository-gij-cloud.md @@ -29,4 +29,5 @@ The webhook is a POST request with the following JSON body: **Result:** -The repository is placed in the indexing queue in the **Git**> **Manage git repositories** configuration page. \ No newline at end of file +The repository is placed in the indexing queue in the **Git**> **Manage git repositories** configuration page. + diff --git a/git-integration-for-jira-cloud/how-to-get-a-quote-gij-cloud.md b/git-integration-for-jira-cloud/how-to-get-a-quote-gij-cloud.md index 4ee8ac7..bf4e2a8 100644 --- a/git-integration-for-jira-cloud/how-to-get-a-quote-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-to-get-a-quote-gij-cloud.md @@ -21,4 +21,5 @@ Primarily, click this [**Generate quote link**](https://www.atlassian.com/purcha 4. Follow instructions on the next screen to complete this process. -For more information on licensing, see [**Licensing Information, Migration and Transition**](https://bigbrassband.atlassian.net/wiki/spaces/BBBSUPPORT/pages/901120001/Licensing+Information+Migration+and+Transition). \ No newline at end of file +For more information on licensing, see [**Licensing Information, Migration and Transition**](https://bigbrassband.atlassian.net/wiki/spaces/BBBSUPPORT/pages/901120001/Licensing+Information+Migration+and+Transition). + diff --git a/git-integration-for-jira-cloud/how-to-link-branches-to-a-jira-issue-gij-cloud.md b/git-integration-for-jira-cloud/how-to-link-branches-to-a-jira-issue-gij-cloud.md index f3cc6e1..ac7c7f4 100644 --- a/git-integration-for-jira-cloud/how-to-link-branches-to-a-jira-issue-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-to-link-branches-to-a-jira-issue-gij-cloud.md @@ -17,4 +17,5 @@ Create a branch and associate it to a Jira issue: 2. Enter a new branch name on the search box. Mention a Jira issue key in the name to associate it to the said Jira issue. -3. Click the result to create the new branch. \ No newline at end of file +3. Click the result to create the new branch. + diff --git a/git-integration-for-jira-cloud/how-to-link-commits-branches-and-pull-requests-to-a-jira-issue-gij-cloud.md b/git-integration-for-jira-cloud/how-to-link-commits-branches-and-pull-requests-to-a-jira-issue-gij-cloud.md index 5e7e92b..babb23f 100644 --- a/git-integration-for-jira-cloud/how-to-link-commits-branches-and-pull-requests-to-a-jira-issue-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-to-link-commits-branches-and-pull-requests-to-a-jira-issue-gij-cloud.md @@ -9,14 +9,11 @@ taxonomy: For information on linking git commits to Jira, see [**Linking git commits to Jira issues**](https://bigbrassband.atlassian.net/wiki/spaces/GITCLOUD/pages/923238543/Linking+Git+Commits+to+Jira+Issue?src=search). -| | -| --- | -| ### Create a branch and associate it to a Jira issue | -| Associate branches to a Jira issue by inserting the Jira issue key to the branch name when creating them.

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1503526923/github-web-create-branch-sample.png?version=1&modificationDate=1618379895400&cacheVersion=1&api=v2&width=566&height=349) | -| 1. Select the _master_ branch dropdown.

2. Enter a new branch name on the search box. Mention a Jira issue key in the name to associate it to the said Jira issue.

3. Click the result to create the new branch. | +### Create a branch and associate it to a Jira issue +Associate branches to a Jira issue by inserting the Jira issue key to the branch name when creating them.

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/1503526923/github-web-create-branch-sample.png?version=1&modificationDate=1618379895400&cacheVersion=1&api=v2&width=566&height=349) +1. Select the _master_ branch dropdown.

2. Enter a new branch name on the search box. Mention a Jira issue key in the name to associate it to the said Jira issue.

3. Click the result to create the new branch. -| | -| --- | -| ### Create a pull request and associate it to a Jira issue | -| ![](https://bigbrassband.atlassian.net/wiki/download/attachments/1503526923/github-web-create-pull-request-sample.png?version=1&modificationDate=1618379895428&cacheVersion=1&api=v2) | -| 1. Set base and compare as required. (branch to master)

2. Enter a new pull request title on the provided box. Mention a Jira issue key in the title to associate it to the said Jira issue.

3. Also, mentioning a Jira issue key on the description will associate this pull request to the said Jira issue. | \ No newline at end of file + +### Create a pull request and associate it to a Jira issue +![](https://bigbrassband.atlassian.net/wiki/download/attachments/1503526923/github-web-create-pull-request-sample.png?version=1&modificationDate=1618379895428&cacheVersion=1&api=v2) +1. Set base and compare as required. (branch to master)

2. Enter a new pull request title on the provided box. Mention a Jira issue key in the title to associate it to the said Jira issue.

3. Also, mentioning a Jira issue key on the description will associate this pull request to the said Jira issue. \ No newline at end of file diff --git a/git-integration-for-jira-cloud/how-to-link-pull-or-merge-requests-to-a-jira-issue-gij-cloud.md b/git-integration-for-jira-cloud/how-to-link-pull-or-merge-requests-to-a-jira-issue-gij-cloud.md index 6e56de5..ad985b0 100644 --- a/git-integration-for-jira-cloud/how-to-link-pull-or-merge-requests-to-a-jira-issue-gij-cloud.md +++ b/git-integration-for-jira-cloud/how-to-link-pull-or-merge-requests-to-a-jira-issue-gij-cloud.md @@ -17,4 +17,5 @@ Create a pull/merge request and associate it to a Jira issue: 2. Enter a new pull request title on the provided box. Mention a Jira issue key in the title to associate it to the said Jira issue. -3. Also, mentioning a Jira issue key on the description will associate this pull request to the said Jira issue. \ No newline at end of file +3. Also, mentioning a Jira issue key on the description will associate this pull request to the said Jira issue. + diff --git a/git-integration-for-jira-cloud/indexing-triggers-formerly-webhooks-gij-cloud.md b/git-integration-for-jira-cloud/indexing-triggers-formerly-webhooks-gij-cloud.md index c0ecbfd..2deff28 100644 --- a/git-integration-for-jira-cloud/indexing-triggers-formerly-webhooks-gij-cloud.md +++ b/git-integration-for-jira-cloud/indexing-triggers-formerly-webhooks-gij-cloud.md @@ -42,10 +42,10 @@ All the repositories will be reindexed if the URL specified above is activated t There is no support for other HTTP methods such as `DELETE` or `HEAD` . -See [About indexing triggers in Jira Cloud](/git-integration-for-jira-cloud/Indexing-Triggers) for a more detailed information on this topic. +See [About indexing triggers in Jira Cloud](/git-integration-for-jira-cloud/indexing-triggers-gij-cloud) for a more detailed information on this topic. -For more information about triggers and event types, see [Creating reindex triggers for a single repository](/git-integration-for-jira-cloud/creating-indexing-triggers-for-a-single-repository/). +For more information about triggers and event types, see [Creating reindex triggers for a single repository](/git-integration-for-jira-cloud/creating-indexing-triggers-for-a-single-repository-gij-cloud). -[« Reindexing](/git-integration-for-jira-cloud/reindexing-gij-cloud/) +[Reindexing](/git-integration-for-jira-cloud/reindexing-gij-cloud/) -[Localization support »](/git-integration-for-jira-cloud/localization-support-gij-cloud/) \ No newline at end of file +[Localization support](/git-integration-for-jira-cloud/localization-support-gij-cloud/) \ No newline at end of file diff --git a/git-integration-for-jira-cloud/indexing-triggers-gij-cloud.md b/git-integration-for-jira-cloud/indexing-triggers-gij-cloud.md index b9fa23d..5f4b97d 100644 --- a/git-integration-for-jira-cloud/indexing-triggers-gij-cloud.md +++ b/git-integration-for-jira-cloud/indexing-triggers-gij-cloud.md @@ -12,7 +12,7 @@ taxonomy: ## What are indexing triggers and why use them? -Indexing triggers (webhooks) can be an extremely powerful tool that can be configured to activate an immediate re-index of your repositories from remote systems. Your git server can send this near real-time data to Jira when your git data changes. This results in a much faster indexing time where you don’t have to wait for the regular polling interval (see [**General settings**](/git-integration-for-jira-cloud/General-Settings)). +Indexing triggers (webhooks) can be an extremely powerful tool that can be configured to activate an immediate re-index of your repositories from remote systems. Your git server can send this near real-time data to Jira when your git data changes. This results in a much faster indexing time where you don’t have to wait for the regular polling interval (see [**General settings**](/git-integration-for-jira-cloud/general-settings-gij-cloud). Webhooks can be initiated whenever certain actions are performed. For example, you can configure a webhook to execute when: @@ -38,7 +38,7 @@ To use the indexing triggers feature, it must be enabled in the Manage (Git) rep Configure indexing triggers to activate immediate reindex of your repositories from remote systems. -1. From your Jira Cloud dashboard menu, go to Apps ➜ **Git Integration: Repository browser**. (_Alternatively, go to_ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) _Jira Settings ➜ Apps_). +1. From your Jira Cloud dashboard menu, go to Apps ➜ **Git Integration: Repository browser**. (_Alternatively, go to_ _Jira Settings ➜ Apps_). 2. On the sidebar, click **Indexing triggers**. The following screen is displayed. @@ -50,7 +50,7 @@ Configure indexing triggers to activate immediate reindex of your repositories f The webhooks URL can be accessed on the following locations: -1. From your Jira Cloud dashboard menu, go to Apps ➜ **Git Integration: Repository browser**. On the sidebar, click **Indexing triggers**. (_Alternatively, go to_ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) _Jira Settings_ ➜ _Apps**.** On the sidebar, click Indexing triggers_). +1. From your Jira Cloud dashboard menu, go to Apps ➜ **Git Integration: Repository browser**. On the sidebar, click **Indexing triggers**. (_Alternatively, go to_ _Jira Settings_ ➜ _Apps**.** On the sidebar, click Indexing triggers_). ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/gitcloud-indexing-triggers-loc-01(c).png?version=1&modificationDate=1617197700714&cacheVersion=1&api=v2&width=646&height=301) 2. On the Manage Git repositories configuration page, click the Indexing triggers button at the top right of the page. @@ -59,7 +59,7 @@ The webhooks URL can be accessed on the following locations: 3. In the **Manage repository** page of a tracked repository — click on a repository/integration from the git configuration list. Look for the Webhook URL field. ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/git-cloud-webhook-url-repo-list-loc(c).png?version=1&modificationDate=1617197700720&cacheVersion=1&api=v2&width=646&height=206) -4. In the Repository Settings page of a repository in a tracked repository or a single connected repository — on the git configuration page, go to ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Actions ➜ **Show integration repositories**. +4. In the Repository Settings page of a repository in a tracked repository or a single connected repository — on the git configuration page, go to Actions ➜ **Show integration repositories**. * ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/git-cloud-webhook-url-repo-cfg-tracked-repos(c).png?version=1&modificationDate=1617197700722&cacheVersion=1&api=v2&width=625&height=196) * ![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/jira-cloud-repo-cfg-view-tracked-repo-dlg(c).png?version=1&modificationDate=1617197700725&cacheVersion=1&api=v2&width=625&height=338) @@ -68,15 +68,14 @@ The **Secret Key** is a secure random-generated alphanumeric string at the tim Use this key in the form of: -[https://gitforjiracloud.bigbrassband.com/api/1/webhook/reindex/install/](https://gitforjiracloud.bigbrassband.com/api/1/webhook/reindex/install/)****/**** +https://gitforjiracloud.bigbrassband.com/api/1/webhook/reindex/install/****/**** Copy the **Webhook URL** to the system clipboard by clicking the copy icon adjacent to the right. Use this URL when required by the repository web hooks setting of your git host. -| | -| --- | | **Example** | +| --- | | Assign your Jira base URL and Secret Key to the example URL structure: | -| [https://gitforjiracloud.bigbrassband.com/api/1/webhook/reindex/install/](https://gitforjiracloud.bigbrassband.com/api/1/webhook/reindex/install/)**x5chdqpqln0j04xcgv02zy7h9**/**vfTmXtqIFyqeCYYS3WjLIn2RRz5rHSDO** | +| https://gitforjiracloud.bigbrassband.com/api/1/webhook/reindex/install/**x5chdqpqln0j04xcgv02zy7h9**/**vfTmXtqIFyqeCYYS3WjLIn2RRz5rHSDO** | **HTTP Method** All the repositories will be reindexed if the URL specified above is activated through `GET`, `POST`, or `PUT` and the webhooks are enabled. @@ -102,20 +101,14 @@ There are three (3) levels of webhook url: Each level references which webhook URL was utilized to configure the webhook: -| | -| --- | -| ### Webhook URL: Install level | -| This is the default webhook URL that is added upon the installation of the Git Integration for Jira app. For this level, events are triggered for all configured repositories.

We recommend to use this webhook URL because it's generally easy to configure and simple to understand.

**Webhook access location:**

* Manage Git repositories sidebar, **Indexing triggers**

* Click **Indexing triggers** button at top right of Manage Git repositories page

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/gitcloud-indexing-trigger-webhook-url-level-1.png?version=1&modificationDate=1617197829120&cacheVersion=1&api=v2&width=584&height=303) | +### Webhook URL: Install level +This is the default webhook URL that is added upon the installation of the Git Integration for Jira app. For this level, events are triggered for all configured repositories.

We recommend to use this webhook URL because it's generally easy to configure and simple to understand.

**Webhook access location:**

* Manage Git repositories sidebar, **Indexing triggers**

* Click **Indexing triggers** button at top right of Manage Git repositories page

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/gitcloud-indexing-trigger-webhook-url-level-1.png?version=1&modificationDate=1617197829120&cacheVersion=1&api=v2&width=584&height=303) -| | -| --- | -| ### Webhook URL: Integration level | -| This webhook URL triggers events only for the repositories within that integration.

**Webhook access location:**

* Manage Git repositories page ➜ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Actions ➜ **Edit integration settings**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/webhook-level-integration.png?version=2&modificationDate=1617197854067&cacheVersion=1&api=v2&width=646&height=301) | +### Webhook URL: Integration level +This webhook URL triggers events only for the repositories within that integration.

**Webhook access location:**

* Manage Git repositories page ➜ Actions ➜ **Edit integration settings**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/webhook-level-integration.png?version=2&modificationDate=1617197854067&cacheVersion=1&api=v2&width=646&height=301) -| | -| --- | -| ### Webhook URL: Repository level | -| This webhook URL triggers events only for the configured repository.

**Webhook access location:**

* Manage Git repositories page ➜ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Actions ➜ **Show integration repositories** ➜ click a repository; or

* Manage Git repositories page ➜ ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Actions ➜ **Edit repository settings**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/webhook-level-repository.png?version=2&modificationDate=1617197898666&cacheVersion=1&api=v2&width=646&height=599) | +### Webhook URL: Repository level +This webhook URL triggers events only for the configured repository.

**Webhook access location:**

* Manage Git repositories page ➜ Actions ➜ **Show integration repositories** ➜ click a repository; or

* Manage Git repositories page ➜ Actions ➜ **Edit repository settings**

![](https://bigbrassband.atlassian.net/wiki/download/thumbnails/171475219/webhook-level-repository.png?version=2&modificationDate=1617197898666&cacheVersion=1&api=v2&width=646&height=599) For indexing to trigger, the repository URL that arrives in the webhook payload must match a repository that is in the Git Integration configuration account. However, it must also match within the webhook level. diff --git a/git-integration-for-jira-cloud/initial-setup-guide-gij-cloud.md b/git-integration-for-jira-cloud/initial-setup-guide-gij-cloud.md index c897a32..e07f97f 100644 --- a/git-integration-for-jira-cloud/initial-setup-guide-gij-cloud.md +++ b/git-integration-for-jira-cloud/initial-setup-guide-gij-cloud.md @@ -12,19 +12,19 @@ Welcome to the initial setup guide. Follow through the topics below to get you s * * * -## ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Connect to a git service +## Connect to a git service -Integrate your favorite git host service to Jira by following the simple steps in [**Working with Git service integration**](/git-integration-for-jira-cloud/git-integration-configuration-page/). +Integrate your favorite git host service to Jira by following the simple steps in [**Working with Git service integration**](/git-integration-for-jira-cloud/git-integration-configuration-page-gij-cloud). -## ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Linking git commits to a Jira issue +## Linking git commits to a Jira issue -Learn how to associate git commits to Jira issues by following the steps in [**Linking git commits to Jira issues**](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues/). +Learn how to associate git commits to Jira issues by following the steps in [**Linking git commits to Jira issues**](/git-integration-for-jira-cloud/linking-git-commits-to-jira-issues-gij-cloud). -## ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Linking branches to a Jira issue +## Linking branches to a Jira issue -Learn how to associate branches to Jira issues by following the simple steps in [**How to link branches to a Jira issue?**](/wiki/spaces/GITCLOUD/pages/2090729485) or see related page on [**Creating git branches inside Jira**](/git-integration-for-jira-cloud/Create-branch). +Learn how to associate branches to Jira issues by following the simple steps in [**How to link branches to a Jira issue?**](/git-integration-for-jira-cloud/how-to-link-branches-to-a-jira-issue-gij-cloud) or see related page on [**Creating git branches inside Jira**](/git-integration-for-jira-cloud/create-branch-gij-cloud). -## ![(blue star)](https://bigbrassband.atlassian.net/wiki/s/-1639011364/6452/8b4898d3c114827e64ec143b4fa79bb76a6cfa5b/_/images/icons/emoticons/star_blue.png) Linking pull or merge requests to a Jira issue +## Linking pull or merge requests to a Jira issue -Learn how to associate branches to Jira issues by following the simple steps in [**How to link pull or merge request to a Jira issue?**](/wiki/spaces/GITCLOUD/pages/2091220997) or see related page on [**Creating pull or merge requests inside Jira**](/git-integration-for-jira-cloud/create-pull-or-merge-request/). +Learn how to associate branches to Jira issues by following the simple steps in [**How to link pull or merge request to a Jira issue?**](/git-integration-for-jira-cloud/how-to-link-pull-or-merge-requests-to-a-jira-issue-gij-cloud) or see related page on [**Creating pull or merge requests inside Jira**](/git-integration-for-jira-cloud/create-pull-or-merge-request-gij-cloud). diff --git a/git-integration-for-jira-cloud/installation-and-setup-gij-cloud.md b/git-integration-for-jira-cloud/installation-and-setup-gij-cloud.md index a8cf634..4fb8487 100644 --- a/git-integration-for-jira-cloud/installation-and-setup-gij-cloud.md +++ b/git-integration-for-jira-cloud/installation-and-setup-gij-cloud.md @@ -55,7 +55,6 @@ Which points to: Go to the section titled, **"Can customers use developer licenses for my add-on?"**, which has instructions on how to get a developer license for add-ons. - In summary: A developer license can be generated (free of charge) once the plugin has been purchased and can only be installed on a development licensed version of Jira. \ No newline at end of file diff --git a/git-integration-for-jira-cloud/installation-via-atlassian-marketplace-gij-cloud.md b/git-integration-for-jira-cloud/installation-via-atlassian-marketplace-gij-cloud.md index de0169d..0671b4b 100644 --- a/git-integration-for-jira-cloud/installation-via-atlassian-marketplace-gij-cloud.md +++ b/git-integration-for-jira-cloud/installation-via-atlassian-marketplace-gij-cloud.md @@ -25,5 +25,5 @@ taxonomy: 5. Start integrating your repositories with Git Integration for Jira Cloud app. -[Installation via Atlassian Marketplace »](/git-integration-for-jira-cloud/installation-via-atlassian-marketplace/) +[Installation via Atlassian Marketplace »](/git-integration-for-jira-cloud/installation-via-atlassian-marketplace-gij-cloud) diff --git a/git-integration-for-jira-cloud/integration-guide-gij-cloud.md b/git-integration-for-jira-cloud/integration-guide-gij-cloud.md index 97e1ea7..117776e 100644 --- a/git-integration-for-jira-cloud/integration-guide-gij-cloud.md +++ b/git-integration-for-jira-cloud/integration-guide-gij-cloud.md @@ -8,7 +8,7 @@ taxonomy: --- Welcome to the Git Integration for Jira app reference page index for topics about integration of git repositories to Jira Cloud. -On this page, you will find the list of integration guides for specific git hosts. For general Jira git integration, see our **[Introduction to Git integration](/git-integration-for-jira-cloud/introduction-to-git-integration/)** to get you more familiar with integration, viewing commits inside Jira, smart commits, and many more. +On this page, you will find the list of integration guides for specific git hosts. For general Jira git integration, see our **[Introduction to Git integration](/git-integration-for-jira-cloud/introduction-to-git-integration-gij-cloud)** to get you more familiar with integration, viewing commits inside Jira, smart commits, and many more. Click on a topic title to view its content or search through the related topics. @@ -26,55 +26,55 @@ Click on a topic title to view its content or search through the related topics. -[GitLab.com](/git-integration-for-jira-cloud/gitlab-com/) +[GitLab.com](/git-integration-for-jira-cloud/gitlab-com-gij-cloud) Connect your GitLab.com remote repositories via Connect to Git Repository wizard or Connect to GitLab wizard. -[GitLab CE/EE Server](/git-integration-for-jira-cloud/gitlab-ce-ee/) +[GitLab CE/EE Server](/git-integration-for-jira-cloud/gitlab-ce-ee-gij-cloud) Connect and manage multiple GitLab server repositories at once via **Connect to GitLab wizard** and the **Show connected repositories** dialog. -[GitHub.com](/git-integration-for-jira-cloud/github-com/) +[GitHub.com](/git-integration-for-jira-cloud/github-com-gij-cloud) Connect your GitHub remote repositories via Connect to Git Repository Wizard. -[GitHub Enterprise Server](/git-integration-for-jira-cloud/github-enterprise-server/) +[GitHub Enterprise Server](/git-integration-for-jira-cloud/github-enterprise-server-gij-cloud) Connect your GitHub Enterprise remote repositories via Connect to Git Repository Wizard. -[Azure DevOps / Visual Studio Team Services (VSTS)](/git-integration-for-jira-cloud/azure-devops-visual-studio-team-services-vsts/) +[Azure DevOps / Visual Studio Team Services (VSTS)](/git-integration-for-jira-cloud/azure-devops-visual-studio-team-services-vsts-gij-cloud) Connect to Visual Studio Team Services (VSTS) / Azure DevOps via Full feature integrations panel in Manage Git repositories. -[Azure DevOps Server | Team Foundation Services (TFS)](/git-integration-for-jira-cloud/azure-devops-server-team-foundation-services-tfs/) +[Azure DevOps Server | Team Foundation Services (TFS)](/git-integration-for-jira-cloud/azure-devops-server-team-foundation-services-tfs-gij-cloud) Connect to Team Foundation Server (TFS) via Full feature integrations panel in Manage Git repositories. -[AWS CodeCommit](/git-integration-for-jira-cloud/AWS-CodeCommit) +[AWS CodeCommit](/git-integration-for-jira-cloud/aws-codecommit-gij-cloud) Connect your AWS CodeCommit repositories via Git Integration for Jira app in Jira Cloud. -[Gerrit](/git-integration-for-jira-cloud/Gerrit) +[Gerrit](/git-integration-for-jira-cloud/gerrit-gij-cloud) Connect your Gerrit repositories via Git Integration for Jira app in Jira Cloud. -[Bitbucket Cloud](/git-integration-for-jira-cloud/Bitbucket-Cloud) +[Bitbucket Cloud](/git-integration-for-jira-cloud/bitbucket-cloud-gij-cloud) Integrate Bitbucket Server git repositories via Git Integration for Jira app using HTTP/SSH connection. From b6906a2a0ca8d02b79d52cdd6fb7bb64181b0b93 Mon Sep 17 00:00:00 2001 From: Shan Florete Date: 2022年6月16日 14:14:35 +0800 Subject: [PATCH 2/3] Delete general-gij-cloud.md --- .../general-gij-cloud.md | 69 ------------------- 1 file changed, 69 deletions(-) delete mode 100644 git-integration-for-jira-cloud/general-gij-cloud.md diff --git a/git-integration-for-jira-cloud/general-gij-cloud.md b/git-integration-for-jira-cloud/general-gij-cloud.md deleted file mode 100644 index 093f077..0000000 --- a/git-integration-for-jira-cloud/general-gij-cloud.md +++ /dev/null @@ -1,69 +0,0 @@ ---- - -title: General -description: -taxonomy: - category: git-integration-for-jira-cloud - ---- -This page contains frequently asked questions by users in general. - -Use the FAQ below to find answers to common questions. Feel free to contact our support team ([support@bigbrassband.com](mailto:support@bigbrassband.com?subject=General%20question%20-)) if you don't see what you're looking for. - -[What is Git?](#General-what-is-git) - -[What is this app?](#General-whatisthisaddon) - -[Why would I want to see Git in my Jira?](#General-seegitinjira) - -[How do Git and Jira work together?](#General-gitandjira) - -[Is this safe? Will it cause trouble?](#General-this-is-safe) - -[Which version of Jira is compatible with Git Integration for Jira add-on?](#General-jiragitaddon) - - - -* * * - - - -## **What is Git?** - -Git is a source code repository. Developers keep track of their source code using Git. Git relies heavily on branching and merging. Branching is making a temporary copy of source code for a single purpose like adding a particular feature or fixing a bug. Merging is safely moving the changes from one branch back to another. - - - -## **What is this app?** - -This is Git Integration for Jira Cloud – an app for Jira that mashes together data from a Git server with your Jira Cloud. It let's people see code from Git in context with Jira issues. - - - -## **Why would I want to see Git in my Jira?** - -Git can be complicated and daunting – especially for non-developers. Jira users want this app so they can work with Git in the familiar Jira interface. - - - -## **How do Git and Jira work together?** - -In organizations with Git and Jira, it is common to have a branch for each Jira issue and branches for every version. - -When developers put their work in Git, they can include a Jira issue key in the comments. With the Git Integration for Jira app installed, Jira Cloud will then show the changes in the issue. - - - -## **Is this safe? Will it cause trouble?** - -It is a safe and well-tested plugin. - -We test this on huge Git repositories in large Jira instances. Over 5000 organizations in 70 countries use the Git Integration for Jira app. - - - -## **Which version of Jira is compatible with Git for Jira Cloud app?** - -For a more comprehensive view, see **[Git Integration for Jira app Version History »](https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/versions "Git add-on Version History")**. - -In the Version History page, you can try or buy the Git Integration for Jira Cloud app or download it for use with **[manual installation »](/git-integration-for-jira-cloud/installation-and-setup-gij-cloud "Git add-on Manual Installation")**. \ No newline at end of file From 81fd4682c4719bfb59f0c0f76647cc785f44246b Mon Sep 17 00:00:00 2001 From: Shan Florete Date: 2022年6月16日 14:15:59 +0800 Subject: [PATCH 3/3] Delete developer-gij-cloud.md --- .../developer-gij-cloud.md | 63 ------------------- 1 file changed, 63 deletions(-) delete mode 100644 git-integration-for-jira-cloud/developer-gij-cloud.md diff --git a/git-integration-for-jira-cloud/developer-gij-cloud.md b/git-integration-for-jira-cloud/developer-gij-cloud.md deleted file mode 100644 index 83e56e0..0000000 --- a/git-integration-for-jira-cloud/developer-gij-cloud.md +++ /dev/null @@ -1,63 +0,0 @@ ---- - -title: Developer -description: -taxonomy: - category: git-integration-for-jira-cloud - ---- -This page contains solutions targeted for developers. - -Use the FAQ below to find answers to common questions. Feel free to contact our support team ([support@bigbrassband.com](mailto:support@bigbrassband.com?subject=Developer%20questions%20-)) if you don't see what you're looking for. - -[How do Git commits get associated with a Jira issue?](#Developer-assocgitcommits) - -[How do I ensure people are following our organization's process for source code?](#Developer-followprocs) - -[What will happen to Jira issue associations with commits if the Jira issue is moved to a new project?](#Developer-issuemovenewproj) - -[Can the plugin be configured to handle or scan multiple keys for one project? How is this supposed to work?](#Developer-handlemultikeys) - - - -* * * - -## **How do Git commits get associated with a Jira issue?** - -On every Git commit, make sure the message includes the exact issue ID at the beginning of the text. The Git Integration for Jira Cloud app will automatically index new commits and associate the referenced issue. - -To create a link between your Git commit and a Jira issue, developers must include the issue key into the commit comment. - -Example git commit message: - -"`PROJ-913 - Plugin version change from 2.6.7 to 2.6.8`"; where **_PROJ-913_** is the issue key that links the commit message to the Jira issue. - - - -## **How do I ensure people are following our organization's process for source code?** - -Open the project summary in your browser and click on the **Git Commits** tab. - -All changes that developers have submitted will be listed in reverse chronologically order. From this view, you can audit all of the changes that developers have recently submitted. - - - -## **What will happen to Jira issue associations with commits if the Jira issue is moved to a new project?** - -The commit retains the association even in the new project. The Git Integration for Jira Cloud app supports history tracking. Thus, when moving a ticket to a new project whose issue key has changed, the association will still work. - -The steps below provides an outline that you can follow to verify that the issue associations with commits are retained: - -1. Associate a commit with issue (ex. **TEST-1**) -2. Move the issue **TEST-1** to a new project (ex. **PM**) -3. New issue key for **TEST-1** is **PM-18** -4. Check that original commit in **TEST-1** is still available in **PM-18**. The commit should be there (Git Commits tab). -5. In the **Git Repositories** configuration page, perform **Reset** and **Reindex** on the selected repository to make sure that the commit was in the correct location. - -The Git Integration for Jira Cloud app also supports multiple issue keys in a commit message. - -## **Can the plugin be configured to handle or scan multiple keys for one project? How is this supposed to work?** - -Yes – the Git Integration for Jira Cloud app supports multiple Jira issue keys in a multiple-line commit message. - -For more information, see **[Smart Commits »](/git-integration-for-jira-cloud/smart-commits-gij-cloud)**. \ No newline at end of file

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