From e6086eab7a17e06c31a6efdb3f117c3529706eda Mon Sep 17 00:00:00 2001 From: Alejandro Gonzalez Recuenco <alejandrogonzalezrecuenco+gitlab@gmail.com> Date: Mon, 25 Mar 2024 23:32:19 +0000 Subject: [PATCH] Update `clickup.md` with custom task Ids info Following *Live Chat Follow-up: with a clickup representative*, this is their recommendation ``` This is because Custom Task IDs require your Workspace/team ID to be present as well. After some further testing, I can confirm that if you use the format below, it will then generate links for both Custom Task IDs and normal task IDs: https://app.clickup.com/t/WorkspaceID/:id You need to replace the WorkspaceID part with your Workspace ID which you can get by simply logging in to your ClickUp account it's the numbers right after app.clickup.com, so as an example for mine: ``` Therefore, although the `t/:id` format still works, since the `t/workspaceId/:id` is more generic, I think it makes sense to just recommend that second one, instead of explaining the differences and when to use one vs the other. --- doc/user/project/integrations/clickup.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/user/project/integrations/clickup.md b/doc/user/project/integrations/clickup.md index 48151368d8db..d190fb3d7ec1 100644 --- a/doc/user/project/integrations/clickup.md +++ b/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`. -- GitLab