Merge branch 'alexrecuenco-master-patch-16221' into 'master'

Update ClickUp integration docs with Custom Task IDs information

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147828



Merged-by: Evan Read <eread@gitlab.com>
Approved-by: Evan Read <eread@gitlab.com>
Co-authored-by: Alejandro Gonzalez Recuenco <alejandrogonzalezrecuenco+gitlab@gmail.com>

doc/user/project/integrations/clickup.md

@@ -34,7 +34,7 @@ which takes you to your ClickUp project.
 For example, this is a configuration for a project named `gitlab-ci`:
 
 - Project URL: `https://app.clickup.com/1234567`
-- Issue URL: `https://app.clickup.com/t/:id`
+- Issue URL: `https://app.clickup.com/t/1234567/:id`
 
 You can also disable [GitLab internal issue tracking](../issues/index.md) in this project.
 For more information about the steps and consequences of disabling GitLab issues, see
@@ -49,6 +49,8 @@ You can reference your ClickUp issues using:
 - `<PROJECT>-<ID>`, for example `API_32-143`, where:
   - `<PROJECT>` is a ClickUp list custom prefix ID.
   - `<ID>` is a number.
+- If you use [Custom Task IDs](https://help.clickup.com/hc/en-us/sections/17044579323671-Custom-Task-IDs), the full custom task ID also works. For
+  example `SOP-1234`.
 
 In links, the `CU-` part is ignored and it links to the global URL of the issue. When a custom
 prefix is used in a ClickUp list, the prefix part is part of the link.
@@ -56,3 +58,5 @@ prefix is used in a ClickUp list, the prefix part is part of the link.
 We suggest using the `CU-` format (`CU-<ID>`) if you have both internal and external issue
 trackers enabled. If you use the shorter format, and an issue with the same ID exists in the
 internal issue tracker, the internal issue is linked.
+
+For [Custom Task IDs](https://help.clickup.com/hc/en-us/sections/17044579323671-Custom-Task-IDs), you **must** include the full ID, including your custom prefix. For example, `SOP-1432`.