Asana added a custom ID field in February 2024, and if a number in a field is all you need, use it. It is built in, it needs nothing extra, and it shows up wherever custom fields show up. This page is about the case that field does not cover. A custom field is not part of the task name, so the number does not travel into a commit message, a pull request title, a file name or the line someone types in a standup. In practice people copy it across, or they describe the task instead of naming it. Astogi writes the number into the task name itself, with a prefix you choose per project. A task called Fix the checkout redirect becomes WEB-0042: Fix the checkout redirect the moment it is created. The number is then part of every notification, export, search result and Git commit that mentions the task, with nothing to copy. Below is how the numbering works, what it does with tasks that already exist, and where the edges are.
Astogi watches the project through an Asana webhook. When a task is added to the project, a queued job reads the task back from Asana, works out the next number and writes the new name. Nothing runs in your browser and nobody has to press anything. The counter belongs to the project, not to the task and not to the workspace. Each project keeps its own number, and the next task takes that number plus one. Two tasks created in the same second cannot end up with the same number, because the counter is read and written under a lock held for that project alone. A busy project and a quiet one never interfere with each other. Before the number comes the prefix, which you set per project. It is built from a few characters at the start, a few in the middle and a divider, and it can include the date the task was numbered: %YY% and %YYYY% for the year, %MM% and %MMM% for the month, %DD% and %DDD% for the day. A prefix of WEB%YY% gives this year's tasks names like WEB26-1 and WEB26-2. The date is expanded when the task is numbered, so next January the same project produces WEB27-3 rather than starting again at one, because the counter runs for the whole project and only ever goes up. Two more settings shape the result. Padding sets how many digits the number has, so a padding of four turns 42 into 0042 and keeps a column of task names aligned. The divider is what sits between the number and the title, a colon by default, which is what produces WEB-0042: Fix the checkout redirect. A task that has already been numbered keeps its number when someone renames it. Astogi stores the identifier it gave the task, and if the number has been edited out of the name it puts it back rather than issuing a new one. A title that already starts with the prefix is left alone, which is what happens when someone duplicates a task: the copy arrives with the original number in its name and Astogi does not touch it, so a duplicate has to be renumbered by hand if you want it to count. Subtasks are opt-in per project. Turn the option on and a subtask takes its own number from the same project counter; leave it off and subtasks are ignored, which keeps the sequence to the work you actually track. Numbering a project that already has a backlog is a separate one-off command rather than something the webhook does, so enabling the integration never rewrites hundreds of existing task names by surprise. And if a project goes over the task allowance of your plan within a rolling 30 days, new tasks are prefixed with E: instead of a number, so you can see at a glance which ones arrived over the limit. The number is only half of it. With Git commit tracking enabled, mention it in a GitHub or Bitbucket commit message and Astogi posts that commit to the matching Asana task, so the task carries the code change without anyone pasting a link.
Yes. Asana added a custom ID field in February 2024, and every task also has an internal id you can see in its URL. The custom ID field is the built-in answer if you only need a number to look at inside Asana. Astogi does something different: it puts the number in the task name, which is why it shows up in commits, exports and chat.
A prefix you set per project, the next number in the sequence, a divider and then the title. With a prefix of WEB and a padding of four, the fourth task in the project is WEB-0004: Fix the checkout redirect.
Yes. The prefix accepts %YY% and %YYYY% for the year, %MM% and %MMM% for the month, %DD% and %DDD% for the day. The date is expanded when the task is numbered, so the prefix follows the calendar while the counter keeps counting up for the whole project.
They keep their names. The webhook only numbers tasks created after the integration is enabled, so turning it on is safe on a project with a long history. To number an existing backlog, run the sync command for that project once.
It keeps its number. Astogi stores the identifier it gave the task, and if the number has been removed from the name it puts it back instead of issuing a new one.
The copy keeps the number of the original, because its title already starts with the prefix and Astogi leaves those alone. If the duplicate should have its own number, remove the prefix from the title and it is numbered on the next sync.
Only if you turn that on for the project. With the option off, subtasks are ignored and the sequence covers top-level tasks only.
A marker for a task created over the task allowance of your plan in a rolling 30 days. Instead of a number it gets E: in front of the title, so you can find those tasks and decide whether to upgrade. Paid plans remove the limit.
Yes. With Git commit tracking enabled, a commit or pull request that mentions the task number is posted to that Asana task, so the change and the task stay in one place.
You can try Astogi for free on your first project. Need more? Get more for just €29/month.
If you have any question or need support, feel free to contact us, our team is always happy to come up with the best solutions to your problems.
Overvoorde 49,
Amsterdam, The Netherlands
Made with ❤️ in the Netherlands
©Astogi 2026
Registered at the
Chamber of Commerce #42271509