Reference numbers for tasks


Awesome creativity!

Asana, strange that someone has to jump through that many hoops to get a feature that seems foundational.

1 Like


I find that the best way to review a bunch of task in a meeting is to create a project about that meeting. You link in all the tasks you want to discuss ahead of time and put them in a section called Agenda.

Before the meeting, you invite your team members and they can link in any tasks they would like to discuss. You can leave conversations, etc., just like any project.

Throughout the meeting, if any new tasks are created, you can add them to a section called Action Items.

Before the meeting is over, you can make sure that all tasks are assigned to someone so they don’t fall through the cracks.

After the meeting is over, you can go through those tasks and put them in the relevant projects, assign custom field values, etc.

This is an old thread, so hopefully you got something figured out, but your use case example seemed perfect for a Meeting project.

Another way to do this would be to create a “Meeting” tag. You could then go through all the tasks you want to discuss in your meeting and tag them. Then, when the meeting starts, everyone can run a report on the tag “Meeting” and they will have the exact list of tasks to discuss.

I think each use case depends on the scope of the meeting.

1 Like

I think the main issue here is that people are thinking about Asana all wrong. They are bringing ideas with them from old paradigms. I’m not saying they are wrong, I’m just saying this different direction that Asana has chosen has caused frustration. But there are different ways of thinking when using Asana that can get you what you want if you step back and look at the problem you are really trying to solve.

In Erik_Graham’s case it was reviewing tasks in a meeting. Creating a meeting project and linking in the tasks to discuss is a very easy and well-supported way to discuss a subset of tasks. That’s one of the main reasons I love Asana (linking a task to more than one project).

Neil_Kessler’s example is a bit different. But sometimes Asana just isn’t the right tool for the job.

I’m not sure why some here chose Asana as a help desk software when there are a lot of other options that have unique IDs, but in my case, I wanted the entire company to be able to use one tool and I felt like Asana was more generic and easier to use in other departments of the company. But to do that, I understood I was giving up some things (that really weren’t that important day-to-day).

As a developer myself, I don’t want to expose my unique IDs to customers because it locks me into whatever system was generating those IDs (often it’s a database). If I want to change it later, I can’t without breaking a million external integrations that my customers created on their own. Imagine how upset you’d be if you spent a bunch of time building a system based off the Asana unique ID and then they changed it. (I would guess that’s one driving force in not making the change.)

1 Like

Hi team,

I also want to use a unique ID to refer to tasks, especially when talking to team mates in Slack, I hate that the task appears automatically with Asana - Slack integration, what I would like is say I have a ticket #123456, well I would love that by typing =123456 or ¤123456 or [123456] or whatever, Asana integration in Slack recognizes it and creates a link or maybe adds the task title, but no preview please, as it f* up conversations.


1 Like

I can’t believe Asana doesn’t feel the need to have task numbers easily configurable and displayed. Have you not worked on a task tracking system before?

Take Jira for example, they have a task number compromised of the project code, and a number. So as per Erik_Graham’s, and other examples above, an example task number would be BC-213.

I could say in a meeting “Everyone look at BC-213”, or I could ask a client who’s not explaining it to me properly, “Please give me the task number, you’ll see it in the email subject, and it will start with ‘BC-’.”
Or I could search my emails for ‘BC-213’, and quickly find all discussions pertaining to this task.
I could ask my clients and staff to include ‘BC-213’ in all correspondence, so as to avoid future confusion.

Why some some people would feel that a task id is not necessary, is beyond me. Unfortunately, this is a deal-breaker for me.

Unfortunately, further. For each of the the tracking systems I’ve tried recently (Asana, Jira, Trello), there is always some kind of silly way of doing things, or lack of a basic feature, making me not want to use the system.

I’m probably just going to create my own one on Gravity Forms, or maybe just stick to Google Sheets. Or maybe I should invest in a rival to Asana, listen to what people need, and make myself an overnight millionaire.


Hi David,

Thanks for the support on this topic. The fight continues to get our task numbers!!

We are too far invested into Asana with thousands of tasks to go elsewhere now. Good luck in your quest!



Our use case goes as follows:
Asana is being used to manage development tasks. When they pick up a task from Asana they need some unique id to use as an identifier when they start making code changes based on the ticket. Task Titles tend to be too long and often contain characters that cannot be used in code branch names. The Task ID is great, except that you cannot come back to Asana and search against it.


Hi James, that is exactly the issue for us also. We are using it to track enhancements to our software between us (support) and the developers and it is a bit of a quagmire without reference numbers.

1 Like

it’s also good for code checkins. Devs can create a git branch with the ticket no, check in and comment re: # and then the the code change reference is in the ticket. Plus what’s been said above about referencing ticket nos.


Please also note this thread: Can a Task have an automatic assigned ID number?