Merge branch '324250-move-first-two-pages' into 'master'

Move pages to new subfolder for jira

See merge request gitlab-org/gitlab!57005

doc/integration/jira/jira_cloud_configuration.md

+---
+stage: Create
+group: Ecosystem
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
+---
+
+# Create an API token in Jira on Atlassian cloud **(FREE)**
+
+For [integrations with Jira](../../user/project/integrations/jira.md), an API token is needed when integrating with Jira
+on Atlassian cloud. To create an API token:
+
+1. Log in to [`id.atlassian.com`](https://id.atlassian.com/manage-profile/security/api-tokens) with your email address.
+
+   NOTE:
+   It is important that the user associated with this email address has *write* access
+   to projects in Jira.
+
+1. Click **Create API token**.
+
+   ![Jira API token](../../user/project/integrations/img/jira_api_token_menu.png)
+
+1. Click **Copy**, or click **View** and write down the new API token. It is required when [configuring GitLab](../../user/project/integrations/jira.md#configure-gitlab).
+
+   ![Jira API token](../../user/project/integrations/img/jira_api_token.png)
+
+The Jira configuration is complete. You need the newly created token, and the associated email
+address, when [configuring GitLab](../../user/project/integrations/jira.md#configure-gitlab).

doc/integration/jira/jira_server_configuration.md

+---
+stage: Create
+group: Ecosystem
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
+---
+
+# Create Jira Server username and password **(FREE)**
+
+For [integrations with Jira](../../user/project/integrations/jira.md), you must create a user account in Jira to have access to
+all projects that need to integrate with GitLab.
+
+The Jira user account created for the integration must have write access to
+your Jira projects.
+
+As an example, the following process creates a user named `gitlab` and that's a
+member of a new group named `gitlab-developers`:
+
+1. Sign in to your Jira instance as an administrator, and
+   then go to the gear icon and select **User Management**.
+
+   ![Jira user management link](../../user/project/integrations/img/jira_user_management_link.png)
+
+1. Create a new user account (for example, `gitlab`) with write access to
+   projects in Jira. Enter the user account's name and a valid e-mail address,
+   because Jira sends a verification email to set up the password.
+
+   Jira creates the username by using the email prefix. You can change the
+   username later, if needed. The GitLab integration doesn't support SSO (such
+   as SAML). You need to create an HTTP basic authentication password. You can
+   do this by visiting the user profile, looking up the username, and setting a
+   password.
+
+   ![Jira create new user](../../user/project/integrations/img/jira_create_new_user.png)
+
+1. From the sidebar, select **Groups**.
+
+   ![Jira create new user](../../user/project/integrations/img/jira_create_new_group.png)
+
+1. In the **Add group** section, enter a **Name** for the group (for example,
+   `gitlab-developers`), and then select **Add group**.
+
+1. Add the `gitlab` user to the `gitlab-developers` group by selecting **Edit members**.
+   The `gitlab-developers` group should be listed in the leftmost box as a
+   selected group. In the **Add members to selected group(s)** area, enter `gitlab`.
+
+   ![Jira add user to group](../../user/project/integrations/img/jira_add_user_to_group.png)
+
+   Select **Add selected users**, and `gitlab` should appear in the **Group member(s)**
+   area. This membership is saved automatically.
+
+   ![Jira added user to group](../../user/project/integrations/img/jira_added_user_to_group.png)
+
+1. To give the newly-created group 'write' access, you must create a permission
+   scheme. To do this, in the admin menu, go to the gear icon and select **Issues**.
+
+1. From the sidebar, select **Permission Schemes**.
+
+1. Select **Add Permission Scheme**, enter a **Name** and (optionally) a
+   **Description**, and then select **Add**.
+
+1. In the permissions scheme list, locate your new permissions scheme, and
+   select **Permissions**. Next to **Administer Projects**, select **Edit**. In
+   the **Group** list, select `gitlab-developers`.
+
+   ![Jira group access](../../user/project/integrations/img/jira_group_access.png)
+
+The Jira configuration is complete. Write down the new Jira username and its
+password, as you need them when [configuring GitLab](../../user/project/integrations/jira.md#configure-gitlab).

doc/user/project/integrations/jira.md

@@ -74,13 +74,13 @@ The process for configuring Jira depends on whether you host Jira on your own se
 Jira Server supports basic authentication. When connecting, a **username and password** are
 required. Connecting to Jira Server via CAS is not possible. For more information, see
-[set up a user in Jira Server](jira_server_configuration.md).
+[set up a user in Jira Server](../../../integration/jira/jira_server_configuration.md).
 #### Jira on Atlassian cloud
 Jira on Atlassian cloud supports authentication through an API token. When connecting to Jira on
 Atlassian cloud, an **email and API token** are required. For more information, see
-[set up a user in Jira on Atlassian cloud](jira_cloud_configuration.md).
+[set up a user in Jira on Atlassian cloud](../../../integration/jira/jira_cloud_configuration.md).
 ### Configure GitLab

doc/user/project/integrations/jira_cloud_configuration.md

 ---
-stage: Create
-group: Ecosystem
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
+redirect_to: '../../../integration/jira/jira_cloud_configuration.md'
 ---
-# Create an API token in Jira on Atlassian cloud **(FREE)**
-For [integrations with Jira](jira.md), an API token is needed when integrating with Jira
-on Atlassian cloud. To create an API token:
-
-1. Log in to [`id.atlassian.com`](https://id.atlassian.com/manage-profile/security/api-tokens) with your email address.
-
-   NOTE:
-   It is important that the user associated with this email address has *write* access
-   to projects in Jira.
-
-1. Click **Create API token**.
-
-   ![Jira API token](img/jira_api_token_menu.png)
-
-1. Click **Copy**, or click **View** and write down the new API token. It is required when [configuring GitLab](jira.md#configure-gitlab).
-
-   ![Jira API token](img/jira_api_token.png)
-
-The Jira configuration is complete. You need the newly created token, and the associated email
-address, when [configuring GitLab](jira.md#configure-gitlab).
+This document was moved to [another location](../../../integration/jira/jira_cloud_configuration.md).
+<!-- This redirect file can be deleted after <2021-06-18>. -->
+<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page -->

doc/user/project/integrations/jira_server_configuration.md

 ---
-stage: Create
-group: Ecosystem
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
+redirect_to: '../../../integration/jira/jira_server_configuration.md'
 ---
-# Create Jira Server username and password **(FREE)**
-For [integrations with Jira](jira.md), you must create a user account in Jira to have access to
-all projects that need to integrate with GitLab.
-
-The Jira user account created for the integration must have write access to
-your Jira projects.
-
-As an example, the following process creates a user named `gitlab` and that's a
-member of a new group named `gitlab-developers`:
-
-1. Sign in to your Jira instance as an administrator, and
-   then go to the gear icon and select **User Management**.
-
-   ![Jira user management link](img/jira_user_management_link.png)
-
-1. Create a new user account (for example, `gitlab`) with write access to
-   projects in Jira. Enter the user account's name and a valid e-mail address,
-   because Jira sends a verification email to set up the password.
-
-   Jira creates the username by using the email prefix. You can change the
-   username later, if needed. The GitLab integration doesn't support SSO (such
-   as SAML). You need to create an HTTP basic authentication password. You can
-   do this by visiting the user profile, looking up the username, and setting a
-   password.
-
-   ![Jira create new user](img/jira_create_new_user.png)
-
-1. From the sidebar, select **Groups**.
-
-   ![Jira create new user](img/jira_create_new_group.png)
-
-1. In the **Add group** section, enter a **Name** for the group (for example,
-   `gitlab-developers`), and then select **Add group**.
-
-1. Add the `gitlab` user to the `gitlab-developers` group by selecting **Edit members**.
-   The `gitlab-developers` group should be listed in the leftmost box as a
-   selected group. In the **Add members to selected group(s)** area, enter `gitlab`.
-
-   ![Jira add user to group](img/jira_add_user_to_group.png)
-
-   Select **Add selected users**, and `gitlab` should appear in the **Group member(s)**
-   area. This membership is saved automatically.
-
-   ![Jira added user to group](img/jira_added_user_to_group.png)
-
-1. To give the newly-created group 'write' access, you must create a permission
-   scheme. To do this, in the admin menu, go to the gear icon and select **Issues**.
-
-1. From the sidebar, select **Permission Schemes**.
-
-1. Select **Add Permission Scheme**, enter a **Name** and (optionally) a
-   **Description**, and then select **Add**.
-
-1. In the permissions scheme list, locate your new permissions scheme, and
-   select **Permissions**. Next to **Administer Projects**, select **Edit**. In
-   the **Group** list, select `gitlab-developers`.
-
-   ![Jira group access](img/jira_group_access.png)
-
-The Jira configuration is complete. Write down the new Jira username and its
-password, as you need them when [configuring GitLab](jira.md#configure-gitlab).
+This document was moved to [another location](../../../integration/jira/jira_server_configuration.md).
+<!-- This redirect file can be deleted after <2021-06-18>. -->
+<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/#move-or-rename-a-page -->