summaryrefslogtreecommitdiff
path: root/doc/integration/jira
diff options
context:
space:
mode:
Diffstat (limited to 'doc/integration/jira')
-rw-r--r--doc/integration/jira/connect-app.md2
-rw-r--r--doc/integration/jira/dvcs.md19
-rw-r--r--doc/integration/jira/img/open_jira_issues_list_v13.2.pngbin90251 -> 0 bytes
-rw-r--r--doc/integration/jira/img/open_jira_issues_list_v14_6.pngbin0 -> 89984 bytes
-rw-r--r--doc/integration/jira/issues.md6
5 files changed, 23 insertions, 4 deletions
diff --git a/doc/integration/jira/connect-app.md b/doc/integration/jira/connect-app.md
index 27f482ee2ba..597293ae5ca 100644
--- a/doc/integration/jira/connect-app.md
+++ b/doc/integration/jira/connect-app.md
@@ -76,7 +76,7 @@ If the app requires additional permissions, [the update must first be manually a
## Install the GitLab.com for Jira Cloud app for self-managed instances **(FREE SELF)**
If your GitLab instance is self-managed, you must follow some
-extra steps to install the GitLab.com for Jira Cloud app.
+extra steps to install the GitLab.com for Jira Cloud app, and your GitLab instance must be accessible by Jira.
Each Jira Cloud application must be installed from a single location. Jira fetches
a [manifest file](https://developer.atlassian.com/cloud/jira/platform/connect-app-descriptor/)
diff --git a/doc/integration/jira/dvcs.md b/doc/integration/jira/dvcs.md
index 2b7cc5ff0a6..e69b7675a59 100644
--- a/doc/integration/jira/dvcs.md
+++ b/doc/integration/jira/dvcs.md
@@ -265,3 +265,22 @@ resynchronize the information:
For more information, read
[Atlassian's documentation](https://support.atlassian.com/jira-cloud-administration/docs/synchronize-jira-cloud-to-bitbucket/).
+
+### `Sync Failed` error when refreshing repository data
+
+If you get a `Sync Failed` error in Jira when [refreshing repository data](#refresh-data-imported-to-jira) for specific projects, check your DVCS connector logs. Look for errors that occur when executing requests to API resources in GitLab. For example:
+
+```plaintext
+Failed to execute request [https://gitlab.com/api/v4/projects/:id/merge_requests?page=1&per_page=100 GET https://gitlab.com/api/v4/projects/:id/merge_requests?page=1&per_page=100 returned a response status of 403 Forbidden] errors:
+{"message":"403 Forbidden"}
+```
+
+If you find a `{"message":"403 Forbidden"}` error, it is possible that this specific project has some [GitLab features disabled](../../user/project/settings/index.md#sharing-and-permissions).
+In the example above, the merge requests feature is disabled.
+
+To resolve the issue, enable the relevant feature:
+
+1. On the top bar, select **Menu > Projects** and find your project.
+1. On the left sidebar, select **Settings > General**.
+1. Expand **Visibility, project features, permissions**.
+1. Use the toggles to enable the features as needed.
diff --git a/doc/integration/jira/img/open_jira_issues_list_v13.2.png b/doc/integration/jira/img/open_jira_issues_list_v13.2.png
deleted file mode 100644
index 0cf58433b25..00000000000
--- a/doc/integration/jira/img/open_jira_issues_list_v13.2.png
+++ /dev/null
Binary files differ
diff --git a/doc/integration/jira/img/open_jira_issues_list_v14_6.png b/doc/integration/jira/img/open_jira_issues_list_v14_6.png
new file mode 100644
index 00000000000..6f06b7fec9a
--- /dev/null
+++ b/doc/integration/jira/img/open_jira_issues_list_v14_6.png
Binary files differ
diff --git a/doc/integration/jira/issues.md b/doc/integration/jira/issues.md
index 70e938a24d4..e24862242e1 100644
--- a/doc/integration/jira/issues.md
+++ b/doc/integration/jira/issues.md
@@ -101,10 +101,10 @@ Consider this example:
You can browse, search, and view issues from a selected Jira project directly in GitLab,
if your GitLab administrator [has configured it](configure.md).
-To do this, in GitLab, go to your project and select **Jira > Issues list**. The issue list
+To do this, in GitLab, go to your project and select **Issues > Jira issues**. The issue list
sorts by **Created date** by default, with the newest issues listed at the top:
-![Jira issues integration enabled](img/open_jira_issues_list_v13.2.png)
+![Jira issues integration enabled](img/open_jira_issues_list_v14_6.png)
- To display the most recently updated issues first, select **Last updated**.
- You can [search and filter](#search-and-filter-the-issues-list) the issues list.
@@ -140,7 +140,7 @@ Enhancements to use these filters through the user interface
## Automatic issue transitions
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/...) in GitLab 13.10.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/55773) in GitLab 13.11.
When you configure automatic issue transitions, you can transition a referenced
Jira issue to the next available status with a category of **Done**. To configure