@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
# Related issues **(FREE)**
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/1797) in [GitLab Starter](https://about.gitlab.com/pricing/) 9.4.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/1797) in GitLab 9.4.
> - The simple "relates to" relationship [moved](https://gitlab.com/gitlab-org/gitlab/-/issues/212329) to [GitLab Free](https://about.gitlab.com/pricing/) in 13.4.
Related issues are a bi-directional relationship between any two issues
...
...
@@ -16,8 +16,8 @@ and projects.
You can set any issue as:
- Related to another issue
- Blocking another issue **(STARTER)**
- Blocked by another issue **(STARTER)**
- Blocking another issue **(PREMIUM)**
- Blocked by another issue **(PREMIUM)**
The relationship only shows up in the UI if the user can see both issues.
...
...
@@ -28,26 +28,28 @@ To manage related issues through our API, visit the [issue links API documentati
## Adding a related issue
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2035) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.8.
> - [Improved](https://gitlab.com/gitlab-org/gitlab/-/issues/34239) to warn when attempting to close an issue that is blocked by others in [GitLab Starter](https://about.gitlab.com/pricing/) 13.0.
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2035) in GitLab 12.8.
> - [Improved](https://gitlab.com/gitlab-org/gitlab/-/issues/34239) to warn when attempting to close an issue that is blocked by others in GitLab 13.0.
> When you try to close an issue with open blockers, you see a warning that you can dismiss.
1. Relate one issue to another by clicking the related issues "+" button
in the header of the related issue block.
1. Select the relationship the between the two issues. Either:
-**relates to**.
-**blocks**. **(PREMIUM)**
-**is blocked by**. **(PREMIUM)**
1. Input the issue reference number or paste in the full URL of the issue.
1.**(STARTER)** Select whether the current issue relates to, blocks, or is blocked by the issues being entered.

Issues of the same project can be specified just by the reference number.
Issues from a different project require additional information like the
group and the project name. For example:
- same project: `#44`
- same group: `project#44`
- different group: `group/project#44`
- The same project: `#44`
- The same group: `project#44`
- Different group: `group/project#44`
Valid references are added to a temporary list that you can review.
...
...
@@ -60,7 +62,7 @@ them categorized so their relationships can be better understood visually.
## Removing a related issue
In the related issues block, click the "x" icon on the right-side of each issue
In the related issues block, click the remove button (**{close}**) on the right-side of each issue
token that you wish to remove.
Due to the bi-directional relationship, it no longer appears in either issue.
msgid "AlertSettings|URL cannot be blank and must start with http or https"
msgstr ""
msgid "AlertSettings|URL is invalid."
msgstr ""
msgid "AlertSettings|Utilize the URL and authorization key below to authorize Prometheus to send alerts to GitLab. Review the Prometheus documentation to learn where to add these details, and the %{linkStart}GitLab documentation%{linkEnd} to learn more about configuring your endpoint."
msgstr ""
...
...
@@ -8726,6 +8723,12 @@ msgstr ""
msgid "Could not load usage counts. Please refresh the page to try again."
msgstr ""
msgid "Could not remove %{user} from %{group}. Cannot remove last group owner."
msgstr ""
msgid "Could not remove %{user} from %{group}. User is not a group member."
msgstr ""
msgid "Could not remove the trigger."
msgstr ""
...
...
@@ -32403,6 +32406,12 @@ msgstr ""
msgid "URL"
msgstr ""
msgid "URL cannot be blank"
msgstr ""
msgid "URL is invalid"
msgstr ""
msgid "URL is required"
msgstr ""
...
...
@@ -33165,6 +33174,9 @@ msgstr ""
msgid "User %{username} was successfully removed."