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
The issue with this is that the tasks can change rows, so you could say to someone âDid you hear anything back about task 4?â and the task in row 4 today might be different than the task in row 4 tomorrow. Row numbers are not permanent, and so canât be used for this purpose.
Here are some other threads about this:
I worked on Facebookâs internal task system for years (after Dustin left to start Asana): we used auto-increment task numbers everywhere. A task needs to be easily reference-able, as we mention them in groups, in other tasks, in diffs and commits, and vocally of course. We even entertained the idea of using mnemonics to refer to individual tasks as the auto-increment numbers got large (never tried this though).
I have no idea what Asanaâs infrastructure looks like, but I feel like it wouldnât be too much work to associate each task with a workspace unique autoincrement ID (or something human memorizable, say under 10MM). Referring to a task like vaultio#123 wouldnât just be nice, itâs essential.
My first impressions with Asana working at my own company, after years of both using and leading development of Facebookâs tasks system, is that perhaps Asana doesnât understand how important integration with other services (internal and external) is to the relative success of a task management system. A human memorizable reference number and a fast, stable API are no brainer first steps here (the former of course not existing, and the latter is very very slow, taking over 3 seconds to cut a task in our anecdotal experience).
I will add my vote to this issue. Much like most others I would be happy enough to have the short-ID be a field that is searchable, not necessarily a part of the URL.
Though if asana would know which domain you belong to since youâre logged in and only search in those. That would allow for a short URL like Log in - Asana that would automatically use the login info, perform a search on your domain, so duplicate IDs are sorted out by cutting down on the namespace scope.
This has been a broken record issue since at least 2013. Same needs, same unworkable workaround suggestions, and then the thread is buried for a bit. I doubt it will change or even be addressed as a problem anytime soon.
You evaluate more than current capabilities when vetting software⌠the lack of any issue ID control and lack of any real markup support (asciidoc, markdown, etc.) are the main âshow stoppersâ for us, but the lack of any way to track Asana tasks (like this one-- itâd be neat if people could track an Asana task for it, versus subscribing to various zombie threads in a forum) also make it hard to swallow. Itâd be great to see Asana using Asana, versus Discourse, basically.
YouTrack does task IDs well, that would be a good model to follow-- you can even set a task ID when importing so as to get a seamless crossover from System X to YouTrack. A smart thing to support if youâre trying to get market share in this space.
+1 !
We would be so grateful to have this feature. A short ID will improve our team communication and will be easier to make a link between PR in git with asana task.
Thereâs nothing quite as unsatisfying as chiming in on a deadhorse topicâŚbut on the off chance that the Product Team at Asana is watching this threadâŚIâll simply say that the absence of this feature is the one show-stopper that is preventing me from bringing my whole team workflows into Asana.
Iâve been a personal user of Asana for yearsâŚbut without this feature I cannot bring my team over onto the serviceâŚitâs a deal killer. #sadness.
46 people asking for the same thing and not one response from Asana⌠no man!?!