Skip to main content
Every task has a short id you can say out loud: WR-142. It is built from the project’s key and a number that counts up inside that project.

​
The format

So WR-142 is the 142nd task created on the project whose key is WR.

​
Where the project key comes from

The key is set when you create a project. TimeTracker suggests one from the project name, and you can change it: The rules behind the suggestion:
  • Two or more words → the initials, capped at five letters.
  • One word → its first three letters.
  • A name with no usable letters → PRJ.
You can edit the key in project settings. See /projects/project-settings.

​
How numbering works

Numbers are allocated per project, in the order tasks are created. Two facts follow:
  • Parents and subtasks share one run. If WR-142 has three subtasks, they are WR-143, WR-144 and WR-145.
  • Numbers are not reused. Delete WR-143 and the next task is still WR-146.
Two projects can have the same number with different keys – WR-142 and MA-142 are different tasks.

​
Where the id appears

On the full task page, one click selects the whole id, so pasting it into a chat or a commit message takes seconds.

​
Why numbers exist

A title changes. “Homepage wireframes” becomes “Homepage wireframes v2” becomes “Homepage layout”. The id does not. That makes the id the right thing to use in:
  • Commit messages and branch names
  • Stand-up notes and chat
  • Invoice line descriptions
  • Anywhere two people need to be certain they mean the same task

​
When a number changes

A task number is permanent within its project. One thing changes it: moving the task to another project. Because numbers are per project, a task moving to a new project is given a fresh number from that project’s sequence. Its subtasks are re-numbered with it. The old number is not reused in the old project. See /tasks/task-details for how a project move works and when it is refused.

​
Example

Northwind Studio runs four projects for its clients: Priya Raman creates “Homepage wireframes” on Website Redesign; it becomes WR-142. She adds two subtasks, which become WR-143 and WR-144. In stand-up she says “Sarah’s on WR-142 today”, and everyone knows exactly what she means. Jonas names his branch wr-142-homepage. Later, WR-144 turns out to belong on the Monthly Retainer instead. Priya moves the parent task across, and it is re-stamped as MR-58. WR-142 is never given to another task.

​
Options and settings

There is nothing to configure on a task. The only choice is the project key, set when you create the project and editable in project settings.

​
Permissions

Task numbers themselves are assigned automatically and cannot be edited.

​
Common questions

No. Numbers are allocated in creation order so they are unique and never collide.
A task was deleted, or moved to another project. Numbers are never reused, so gaps are normal.
Existing tasks show the new key straight away, because the id is composed from the project’s current key and the task’s stored number. WR-142 becomes WEB-142 if you rename the key to WEB.
No. Keys are unique inside a workspace, so an id is never ambiguous.
Use the workspace search from the sidebar. The board’s search box matches titles, not ids.
Very old tasks created before numbering can be missing one. Contact support if you see this on a current workspace.

​
Troubleshooting

It is either the wrong shape – it must be 2 to 5 uppercase letters with no digits – or another project in this workspace already uses it.
The project has no key, or the task has no number. Open project settings and set a key.
Check you are both in the same workspace. Keys are unique inside one workspace, not across all of TimeTracker.

Project settings

Where the project key is set.

Task details

Moving a task, and its new number.

Subtasks

Parents and subtasks share one run.

Create a project

Choosing a key at the start.

Glossary

Every term in one place.