diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/administration/geo/replication/datatypes.md | 48 | ||||
| -rw-r--r-- | doc/integration/img/jira_dev_panel_setup_com_1.png | bin | 0 -> 50565 bytes | |||
| -rw-r--r-- | doc/integration/img/jira_dev_panel_setup_com_2.png | bin | 0 -> 66881 bytes | |||
| -rw-r--r-- | doc/integration/img/jira_dev_panel_setup_com_3.png | bin | 0 -> 24910 bytes | |||
| -rw-r--r-- | doc/integration/jira_development_panel.md | 42 | ||||
| -rw-r--r-- | doc/user/group/subgroups/index.md | 4 |
6 files changed, 68 insertions, 26 deletions
diff --git a/doc/administration/geo/replication/datatypes.md b/doc/administration/geo/replication/datatypes.md index feb0c2f2f4d..f8c3076a38c 100644 --- a/doc/administration/geo/replication/datatypes.md +++ b/doc/administration/geo/replication/datatypes.md @@ -124,28 +124,29 @@ replicating data from those features will cause the data to be **lost**. If you wish to use those features on a **secondary** node, or to execute a failover successfully, you must replicate their data using some other means. -| Feature | Replicated | Verified | Notes | -|-----------------------------------------------------|--------------------------|-----------------------------|---------------------------------------------| -| Application data in PostgreSQL | **Yes** | **Yes** | | -| Project repository | **Yes** | **Yes** | | -| Project wiki repository | **Yes** | **Yes** | | -| Project designs repository | **Yes** | [No][design-verification] | | -| Uploads | **Yes** | [No][upload-verification] | Verified only on transfer, or manually (*1*)| -| LFS objects | **Yes** | [No][lfs-verification] | Verified only on transfer, or manually (*1*). Unavailable for new LFS objects in 11.11.x and 12.0.x (*2*). | -| CI job artifacts (other than traces) | **Yes** | [No][artifact-verification] | Verified only manually (*1*) | -| Archived traces | **Yes** | [No][artifact-verification] | Verified only on transfer, or manually (*1*)| -| Personal snippets | **Yes** | **Yes** | | -| Project snippets | **Yes** | **Yes** | | -| Object pools for forked project deduplication | **Yes** | No | | -| [Server-side Git Hooks][custom-hooks] | No | No | | -| [Elasticsearch integration][elasticsearch] | No | No | | -| [GitLab Pages][gitlab-pages] | [No][pages-replication] | No | | -| [Container Registry][container-registry] | **Yes** | No | | -| [NPM Registry][npm-registry] | No | No | | -| [Maven Repository][maven-repository] | No | No | | -| [Conan Repository][conan-repository] | No | No | | -| [External merge request diffs][merge-request-diffs] | [No][diffs-replication] | No | | -| Content in object storage | **Yes** | No | | +| Feature | Replicated | Verified | Notes | +|-----------------------------------------------------|-------------------------- |-----------------------------|---------------------------------------------| +| Application data in PostgreSQL | **Yes** | **Yes** | | +| Project repository | **Yes** | **Yes** | | +| Project wiki repository | **Yes** | **Yes** | | +| Project designs repository | **Yes** | [No][design-verification] | | +| Uploads | **Yes** | [No][upload-verification] | Verified only on transfer, or manually (*1*)| +| LFS objects | **Yes** | [No][lfs-verification] | Verified only on transfer, or manually (*1*). Unavailable for new LFS objects in 11.11.x and 12.0.x (*2*). | +| CI job artifacts (other than traces) | **Yes** | [No][artifact-verification] | Verified only manually (*1*) | +| Archived traces | **Yes** | [No][artifact-verification] | Verified only on transfer, or manually (*1*)| +| Personal snippets | **Yes** | **Yes** | | +| Project snippets | **Yes** | **Yes** | | +| Object pools for forked project deduplication | **Yes** | No | | +| [Server-side Git Hooks][custom-hooks] | No | No | | +| [Elasticsearch integration][elasticsearch] | [No][elasticsearch-replication] | No | | +| [GitLab Pages][gitlab-pages] | [No][pages-replication] | No | | +| [Container Registry][container-registry] | **Yes** | No | | +| [NPM Registry][npm-registry] | [No][packages-replication] | No | | +| [Maven Repository][maven-repository] | [No][packages-replication] | No | | +| [Conan Repository][conan-repository] | [No][packages-replication] | No | | +| [NuGet Repository][nuget-repository] | [No][packages-replication] | No | | +| [External merge request diffs][merge-request-diffs] | [No][diffs-replication] | No | | +| Content in object storage | **Yes** | No | | - (*1*): The integrity can be verified manually using [Integrity Check Rake Task](../../raketasks/check.md) on both nodes and comparing @@ -160,6 +161,8 @@ successfully, you must replicate their data using some other means. [artifact-verification]: https://gitlab.com/gitlab-org/gitlab/issues/8923 [diffs-replication]: https://gitlab.com/gitlab-org/gitlab/issues/33817 [pages-replication]: https://gitlab.com/groups/gitlab-org/-/epics/589 +[packages-replication]: https://gitlab.com/groups/gitlab-org/-/epics/2346 +[elasticsearch-replication]: https://gitlab.com/gitlab-org/gitlab/-/issues/1186 [custom-hooks]: ../../custom_hooks.md [elasticsearch]: ../../../integration/elasticsearch.md @@ -168,4 +171,5 @@ successfully, you must replicate their data using some other means. [npm-registry]: ../../../user/packages/npm_registry/index.md [maven-repository]: ../../../user/packages/maven_repository/index.md [conan-repository]: ../../../user/packages/conan_repository/index.md +[nuget-repository]: ../../../user/packages/nuget_repository/index.md [merge-request-diffs]: ../../merge_request_diffs.md diff --git a/doc/integration/img/jira_dev_panel_setup_com_1.png b/doc/integration/img/jira_dev_panel_setup_com_1.png Binary files differnew file mode 100644 index 00000000000..906e4aa16cb --- /dev/null +++ b/doc/integration/img/jira_dev_panel_setup_com_1.png diff --git a/doc/integration/img/jira_dev_panel_setup_com_2.png b/doc/integration/img/jira_dev_panel_setup_com_2.png Binary files differnew file mode 100644 index 00000000000..002a9140968 --- /dev/null +++ b/doc/integration/img/jira_dev_panel_setup_com_2.png diff --git a/doc/integration/img/jira_dev_panel_setup_com_3.png b/doc/integration/img/jira_dev_panel_setup_com_3.png Binary files differnew file mode 100644 index 00000000000..c4e748c38cf --- /dev/null +++ b/doc/integration/img/jira_dev_panel_setup_com_3.png diff --git a/doc/integration/jira_development_panel.md b/doc/integration/jira_development_panel.md index 754c4a4148c..2f365cc04da 100644 --- a/doc/integration/jira_development_panel.md +++ b/doc/integration/jira_development_panel.md @@ -67,6 +67,8 @@ There are no special requirements if you are using GitLab.com. ## Jira Configuration +### GitLab self-managed + 1. In Jira, go to **Jira Settings > Applications > DVCS accounts**, then click **Link GitHub Enterprise account** to start creating a new integration. (We are pretending to be GitHub in this integration until there is further platform support from Jira.) @@ -110,7 +112,45 @@ There are no special requirements if you are using GitLab.com. To connect additional GitLab projects from other GitLab top-level groups (or personal namespaces), repeat the above steps with additional Jira DVCS accounts. -You may now refer any Jira issue by its ID in branch names, commit messages and merge request names on GitLab's side, +### GitLab.com + +You can integrate GitLab.com and Jira Cloud using the **GitLab for Jira** App in the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1221011/gitlab-for-jira). + +GitLab and Jira can also be integrated using the DVCS connector as described in the [GitLab self-managed section](#gitlab-self-managed). The [GitLab for Jira App](https://marketplace.atlassian.com/apps/1221011/gitlab-for-jira) is recommended when using GitLab.com and Jira Cloud because data is synchronized in real time, while the DVCS connector updates data only once per hour. + +<i class="fa fa-youtube-play youtube" aria-hidden="true"></i> +For a walkthrough of the integration with GitLab for Jira, watch [Configure GitLab Jira Integration using Marketplace App](https://youtu.be/SwR-g1s1zTo) on YouTube. + +NOTE: **Note:** +The **GitLab for Jira** App is only compatible with GitLab.com **and** Jira Cloud. + +1. Go to **Jira Settings > Apps > Find new apps**, then search for GitLab. +1. Click **GitLab for Jira**, then click **Get it now**. Or go the [App in the marketplace directly](https://marketplace.atlassian.com/apps/1221011/gitlab-for-jira) + +  +1. After installing, click **Get started** to go to the configurations page. This page is always available under **Jira Settings > Apps > Manage apps**. + +  +1. Enter the group or personal namespace in the **Namespace** field and click **Link namespace to Jira**. Make sure you are logged in on GitLab.com and the namespace has a Silver or above license. The user setting up _GitLab for Jira_ must have **Maintainer** access to the GitLab namespace. + +NOTE: **Note:** +The GitLab user only needs access when adding a new namespace. For syncing with Jira, we do not depend on the user's token. + +  + +After a namespace is added, all future commits, branches and merge requests of all projects under that namespace will be synced to Jira. Past data cannot be synced at the moment. + +#### Troubleshooting GitLab for Jira + +The GitLab for Jira App uses an iframe to add namespaces on the settings page. Some browsers block cross-site cookies which can lead to a message saying that the user needs to log in on GitLab.com even though the user is already logged in. + +> "You need to sign in or sign up before continuing." + +In this case, enable cross-site cookies in your browser. + +## Usage + +Once the integration is set up on GitLab and Jira you may refer any Jira issue by its ID in branch names, commit messages and merge request titles on GitLab's side, and you will be able to see the linked `branches`, `commits`, and `merge requests` when entering a Jira issue (inside the Jira issue, merge requests will be called "pull requests"). diff --git a/doc/user/group/subgroups/index.md b/doc/user/group/subgroups/index.md index 997cb1ba6c5..5ff8243136e 100644 --- a/doc/user/group/subgroups/index.md +++ b/doc/user/group/subgroups/index.md @@ -6,7 +6,7 @@ type: reference, howto, concepts > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/2772) in GitLab 9.0. -Subgroups, also known as nested groups or hierarchical groups, allow you to have up to 20 +GitLab supports up to 20 levels of subgroups, also known as nested groups or hierarchical groups. levels of groups. By using subgroups you can do the following: @@ -64,8 +64,6 @@ Another example of GitLab as a company would be the following: --- -The maximum subgroups a group can have, including the first one in the -hierarchy, is 21. When performing actions such as transferring or importing a project between subgroups, the behavior is the same as when performing these actions at the |
