ClickUp Custom Task IDs: Prefixes, Plans, and Git Links

Every ClickUp task already has an ID. It sits in the task URL, in the task modal, and as a column you can add in List view. That ID is on every plan. A custom task ID is a second label, shaped like a ticket: a prefix, a hyphen, and a number, such as CLK-1. Help limits custom task IDs to the Business plan and above. A Workspace owner or admin turns the ClickApp on, picks the Spaces, and sets the prefix and the first number.

The ordinary ID never goes away. Open a task and double click the custom ID to see the original. Software teams use the prefixed form in branches and pull requests. That link is covered in ClickUp GitHub integration. The product index is the ClickUp hub.

What is a ClickUp custom task ID?

A custom task ID belongs to a Space, not to a single List. When you enable the ClickApp for a Space, ClickUp asks for two values.

Setting	Rule from Help
Prefix	Always uppercase. Letters, numbers, and underscores only. Unique across Spaces
Starting index	A number greater than 0

Tasks already in the Space receive IDs by date created, oldest first. Help's example: prefix CLK and starting index 1. The oldest task becomes CLK-1. Newer tasks take the next numbers. Subtasks are included automatically. You do not number them by hand.

The ordinary task ID is a different string. Help says you can find it at the end of the task URL, by clicking the task ID icon above the title, or from the task settings menu with Copy ID. In List view, add the Task ID column from the plus icon above the table, then click a cell to copy it. You can also search List view by that ID. None of that requires Business. Custom IDs are the prefixed layer on top.

Custom task types are easy to confuse with this. A type is a name and an icon, such as Bug or Invoice, and Free Forever includes a limited number of uses. An ID is the ticket code. A bug can be type Bug and ID ENG-104 at the same time. One does not create the other.

How do you enable and edit custom task IDs?

Owners and admins enable the ClickApp. Members cannot.

1. Open the App Center.
2. In the left sidebar, click All ClickApps.
3. Search for Custom Task IDs and turn the toggle on.
4. Use the dropdown if you want the ClickApp in specific Spaces only.

Enabling it for a Space opens the prefix and starting index prompt. After the IDs exist, an owner or admin can change them:

1. In the Home Sidebar or the Spaces Sidebar, hover the Space and click the ellipsis, or right click the Space.
2. Hover More, then click Customize Task IDs.
3. Update the ID and click Save.

You can change a prefix later, including back to a prefix that Space used before. You cannot give it a prefix another Space is using. Help also says a deleted Space keeps its prefix forever. Those IDs are no longer available, and the prefix cannot be reused on a new Space. Pick prefixes you are willing to keep: ENG, DES, OPS, or a client code, not a temporary joke.

To show the IDs where people work:

View	How to show the custom ID
List	Click the plus icon above the task table and select Custom Task ID
Board	Click Customize, select Fields, and enable Custom Task ID

The List column and the Board field are display options. Turning them on does not create the IDs. The ClickApp does that.

In a comment, type @@ and search the custom ID. Help says the unfurled mention shows both the custom ID and the task name. That is the practical reason to bother with prefixes: a sentence in Chat or in a Doc can point at ENG-104, and a reader who does not live in that Space still sees the name.

How do custom task IDs work with GitHub, GitLab, and Bitbucket?

Help points custom IDs at the git integrations: GitHub, GitLab, and Bitbucket. The pattern is the same one the ordinary ID uses. Put the ID in the branch name, commit message, or pull request title, and ClickUp attaches the activity to the task.

One constraint matters if you also use Tasks in Multiple Lists. Help says the repository must be linked to the Space that contains the task's Home List. Linking the repo to a different Space, one that only holds an additional copy of the task, does not work. If a task lives in an engineering List and is also added to a client List, connect GitHub to the engineering Space when that Space holds the Home List. The Home List idea is in tasks in multiple lists.

Ordinary task IDs already work with those integrations on every plan. Custom IDs are worth Business when the team speaks in ticket codes, when support staff paste IDs into email, or when several Spaces would otherwise share one opaque ClickUp ID format. A three person team that never types an ID can stay on the built in ID and skip the ClickApp.

Sprint folders and points are a separate setup. ClickUp for software teams and ClickUp sprints cover that side. A custom ID does not create a sprint, and a sprint does not require a custom ID.

What happens when a task moves between Spaces?

Help's FAQ is specific. The underlying ClickUp task ID never changes. The custom ID depends on the Space the task lands in.

Move	Custom ID
From a Space with custom IDs to a Space without them	You can still reference the task by the original ClickUp ID or by the custom ID it had
From one prefixed Space to another prefixed Space	The task receives a new custom ID from the destination Space, because the prefixes differ
From a Space without custom IDs into a prefixed Space	The task takes the next available custom ID in that Space. Both IDs still work
Space is deleted	Custom IDs inside it are no longer available. The prefix cannot be reused

Double click the custom ID on an open task whenever you need the original. Scripts, old commit messages, and bookmarks that used the ClickUp ID keep working after you turn custom IDs on. Messages that cited CLK-14 may point at a different number after a move to a Space whose prefix is not CLK. If you reorganize Spaces, update the links people have memorized, or keep the prefix stable and move Lists inside the Space instead of moving tasks across prefixes.

Which plan do you need?

Custom task IDs start on Business. Our pricing data, checked October 2026, lists Business at $12 per user per month billed annually, or $19 monthly. Unlimited, at $7 annually or $10 monthly, includes the ordinary task ID and the git integration, and it does not include this ClickApp. Enterprise is custom. The plan table and what else Business adds is in ClickUp pricing.

Buy Business for the IDs only if people outside the task view need a code they can say out loud. A support inbox, a GitHub branch, and a status meeting all get easier when the code is ENG-104 instead of a string from the URL. If the team never leaves ClickUp, the ID that is already on Free Forever is enough, and the money is better spent on a feature you will open every day.