@@ -141,32 +141,43 @@ This checks if an email suppression exists within Mailgun. Depending on the resu
#### Link Tagger
<sup>Introduced via [gitlab-com/support/support-ops/support-ops-project#998](https://gitlab.com/gitlab-com/support/support-ops/support-ops-project/-/issues/998)</sup>
<sup>Introduced to Zendesk Global via [gitlab-com/support/support-ops/support-ops-project#998](https://gitlab.com/gitlab-com/support/support-ops/support-ops-project/-/issues/998) and to Zendesk US Government via [gitlab-com/gl-security/corp/cust-support-ops/issue-tracker#841](https://gitlab.com/gitlab-com/gl-security/corp/cust-support-ops/issue-tracker/-/work_items/841)</sup>
This checks the passed comment (public and made be an agent) for the various types of items we would want to tag on the ticket. The current kinds of items (and the tag added based on them) are as follows:
- Contains a gitlab.com issue link
-`gitlab_issue_link` tag is added
-`CUSTOMPATH_issues_IID` tag is added
-`CUSTOMPATH_issues_IID` tag is added (Global only)
-`CUSTOMPATH` is the project's slug, `IID` is the issue ID
- Example: a link to issue 5 on project jcolyer/most_amazing_project_ever would be: `jcolyer_most_amazing_project_ever_issues_5`
-`issue~CUSTOMPATH_IID`
-`CUSTOMPATH` is the project's slug, `IID` is the issue ID
- Example: a link to issue 5 on project jcolyer/most_amazing_project_ever would be: `issue~jcolyer_most_amazing_project_ever_issues_5`
-`issue_PROJECTID_IID`
-`issue_PROJECTID_IID` (Global only)
-`PROJECTID` is the project's ID, `IID` is the issue ID
- Example: a link to issue 5 on project jcolyer/most_amazing_project_ever (project ID 123) would be: `issue_123_5`
- Contains a gitlab.com merge request link
-`gitlab_merge_request_link` tag is added
-`CUSTOM_PATH_merge_requests_IID` tag is added
-`CUSTOM_PATH_merge_requests_IID` tag is added (Global only)
-`CUSTOMPATH` is the project's slug, `IID` is the merge request ID
- Example: a link to merge request 27 on project jcolyer/most_amazing_project_ever would be: `jcolyer_most_amazing_project_ever_merge_requests_27`
-`mergerequest~CUSTOMPATH_IID`
-`CUSTOMPATH` is the project's slug, `IID` is the issue ID
- Example: a link to merge request 27 on project jcolyer/most_amazing_project_ever would be: `mergerequest~jcolyer_most_amazing_project_ever_27`
-`mergerequest_PROJECTID_IID`
-`mergerequest_PROJECTID_IID` (Global only)
-`PROJECTID` is the project's ID, `IID` is the merge request ID
- Example: a link to merge request 27 on project jcolyer/most_amazing_project_ever (project ID 123) would be: `mergerequest_123_27`
- Contains a gitlab.com epic link
-`gitlab_epic_link` tag is added
-`CUSTOMPATH_epic_IID` tag is added (Global only)
-`CUSTOMPATH` is the project's slug, `IID` is the epic ID
- Example: a link to epic 10 on project jcolyer/most_amazing_project_ever would be: `jcolyer_most_amazing_project_ever_epic_10`
-`epic~CUSTOMPATH_IID`
-`CUSTOMPATH` is the project's slug, `IID` is the epic ID
- Example: a link to epic 10 on project jcolyer/most_amazing_project_ever would be: `epic~jcolyer_most_amazing_project_ever_10`
-`epic_PROJECTID_IID` (Global only)
-`PROJECTID` is the project's ID, `IID` is the epic ID
- Example: a link to epic 10 on project jcolyer/most_amazing_project_ever (project ID 123) would be: `epic_123_10`
- Contains a docs.gitlab.com link
-`docs_link` tag is added
- Contains a handbook.gitlab.com link
@@ -267,6 +278,7 @@ The following items work identically to Zendesk Global:
