Hi,
Very much would like to see this implemented. I have used Jira in the past and I am a web developer trying to use it for projects and bug management. Having a Project code and issue numbers would be my preference and hope you consider making it a high feature request.
Maybe @Alexis may help on the matter?
I have a similar question, regarding how to generate an unique ID to tasks.
I need to have an unique identifier to tasks that are in 3 different projects. I tought that having a drop-down custom field would work, but I quickly hit the limit (with is 50 items per drop down list). So I need help!
How can I create a unique ID for tasks in different projets (i.e.: task ID# 00001 in project ABC, Task ID# 00002 in project DEF, Task ID# 00003 in project ABC, Task ID# 00004 in projet GHI,…)?
Anyone can help me?
I think I may move back to JIRA just because of this reason.
We have exactly the same issue. We need a short number for our Git branches as we want to use the task # in our branch names.
Yeah I second this motion, Asana - just add the field, short URL it!
Example:
Log in - Asana{project name/id}/{id}
Or
https://{company}.asana.com/{project name/id}-{id}
Looking forward to this feature. Without this feature, it’s hard to let developers use Asana.
We really just need a short Auto-Incrementing ID for each new task to track it and reference it in team discussions and code commits. Something as simple as “Issue #123 - Task Title” would suffice.
Steve_Kostrey - This suggestion is spot on. This is how Jira does it. Pretty straight forward. Simple, but great feature.
It’s not only Jira, you need ticket numbers to keep track of features. It is implemented in a lot of systems. I appreciate the explanation why YUO need long IDs but that is another thing.
People here needs numbers relative to the project and I don’t get why after a year you didn’t implemented yet.
I need ticket numbers and if I can’t get it here, I’ll find something else, along the entire company…
I agree. Referencing tasks inside git commits is practically impossible with Asana. Fix this please.
Company has just moved to Asana; without this feature it’s impossible to reference Asana task numbers on our physical tracking board.
Please implement.
This would be exceptionally useful, and the lack of this feature is making Asana difficult to use. If we want to talk about a task we can’t refer to it as “hey, did you work on 668839374825240/707209820347285?” in conversation or refer to that in comments or emails and have anyone know what we’re talking about. Even when we’re trying to link or reference tasks WITHIN Asana it’s hard to do so using the @ notation because there’s no way to easily refer to tasks. The summary of a lot of tasks can be similar, and you only see the first few words of each one, so it’s difficult to reference them through @ notation correctly when the first couple of words match.
You’ve hit the nail on the head with your description of how useless those long identifiers are in the real world.
I don’t really care if the URL is what it currently is (though short links would be nice) but just having SOME auto-generated, user-friendly identifier would be a huge help. YouTrack does this really nicely by assigning a serial number to each item along with a project abbreviation (which you come up with yourself). For example, if we had a Marketo integration project which we abbreviate as MKTO each ticket which is created would have a user-friendly ID of MKTO-1, MKTO-2, MKTO-3, etc. automatically generated as tickets are created. You can then use @notation to refer to tickets using these values, such as as “What is the status of @MKTO-2?” which would link to the MKTO-2 ticket.
It would be very helpful if we could do something similar in Asana, giving each project an abbreviation and then having tickets be assigned a serial number for the project they are created in (even if they’re added to a different project later) so that we can @reference them easily.
I think that to have a short URL like “Log in - Asana” which some other people mentioned we’d need to have workspaces with unique shortnames as part of the URL, either as a part of the path or as a subdomain. The workspace shortname might be auto-assigned or customizable by the user, but it would need to be unique. Projects within a workspace would also need to have their own, unique-within-a-workspace shortname. You could end up with a path of “https://mysworkspace.app.asana.com/HR-206” or “Log in - Asana”.
Even with the longer URLs, however, it’s still extremely useful to have a short name like HR-206 to refer to tasks by, both for @notation and for URLs and references in emails, where you can show the short name but the URL can go to the longer link. A short URL showing up in the address bar would save you some steps if you’re copying and pasting a link in an email so that the end user might know what you’re talking about without even clicking a link, but just having the short task ID generated in the first place would go a long way to easing communication about these issues.
Developer here. There’s no reason the ID’s have to be big if you had Projects/Tasks scoped per domain. Those ID’s should start at 1 instead of using their SQL ID ( which is what I’m assuming you’re doing ). If you update this, we will take you guys up in business.
We would love this feature too! So much easier to have a short ID for each task.
We’re evaluating Asana currently as on option to replace our main task system, and the lack of shortish, meaningful task IDs, is kind of a show stopper for us, for reasons well covered here.
In short, one of the key bits of reference for a ticketing system (the ticket, or its ID if you prefer) is unwieldy to use. Not just in Asana, but outside, IRL too.
We love the social interface, and things are fine with ~8 users and medium throughput, but we’re looking for a solution for multiple teams of people with reams of tickets, and it’s seeming like Asana is not geared for large teams, or small teams with lots of tickets.
Manual naming strategies, shadow systems, or link shrinks are not appealing workarounds for the problem.
It’s also kind of concerning that there’s only been what looks to be one response by someone from Asana, a year ago. Is this issue on the radar? Something in the works hopefully?
Is there maybe an Asana task system for Asana tasks that I should be posting this to instead? Sorry for the grocery list, but while I’m at it, sorting by votes would probably be a handy metric to expose-- ah, I see “votes” here but “likes” in other categories, so this probably is the issue system as well as the community portal.
It’d be cool to have this bit actually be in Asana, i.e. “dogfooding”, similar to how some other systems do it… anyhow, the IDs is the main thing, just tossed in the stuff about feedback in general when it struck me.
Great product overall, just a couple issues making it tough for us to spring for it.
I’d like to propose that Asana adds task ID’s. Usually when working in a team, it’s helpful to be able to speak a task ID like “Task 12”, and the others on the call will easily be able to spot the task in asana, or be able to find it by sorting.
The task ID should simply be the ordinal number of the task created within the project.
This idea is taken from Jira task ID’s.
You can enable row numbers and refer to the ‘task row 12’ for all the projects, etc.
They talk about it here, it’s under your ‘my profile settings’ - How to Control Your Profile Settings in Asana | Product guide • Asana Product Guide