Thanks Larry!
@lpb Got excited there for a moment, thought they might have released a new feature for this. lol
Keeping my fingers crossed
that 2025 is the year they release a relation field. This would complete our Asana Lite CRM.
We recently decided to move our agencyās lite CRM from Asana to HubSpot, mainly because Asana doesnāt support a ārelationshipā custom field. I get that Asana and HubSpot are built for different things, but honestly, nothing beats Asanaās UI and flexibility ā we really miss that now. Itās such a great platform, and with just a few tweaks like this, it could easily support simple CRM needs too. Hoping the Asana team considers adding this soon ![]()
Oh dear. 2025 and still you canāt link tasks (ārelatedā)⦠NO, putting text links in custom filed os not a workaround. THERE IS NO WORKAROUND FOR THIS in Asana, this is the most painful part. Such a basic feature, so much requested over the yearsā¦
Iām starting to wonder if relating projects though lookup fields is too ādatabaseyā for Asana and the reticence over implementing what is arguably the easiest form of linking may be more a matter of philosophy vs technical? If so, it would be nice to know as that would mean we could effectively stop hoping for this type of enhancement and figure out the future built exclusively around multi-homingā¦
@Geoffrey_Brandt I would definitely not make that assumption. Donāt stop hoping⦠![]()
Iāll make a sacrifice to the related field god.
I wonder if Asana actually listens to user feedback. This functionality canāt actually be that difficult to implement. It would be good to have some transparency from Asana on this.
They definitely do listen. We (Forum Leaders) wrote a post about it recently š¦ If Wishes Were Unicorns: Why Asana Might Not Have Implemented that Feature Request (and other thoughts about Asana feature development and product strategy)
Just got out of a meeting with our developer vendor in which a related task field would solve a big problem. Since we canāt do it Iāll have to use both Asana (for internal use) and Azure Dev-Ops (for vendor use). The only workaround I can think of is asking our team to link to another task in a comment and then pin that comment. This would still be easy to miss, and we might have other pinned comments detailing specifics of the work. We canāt use dependencies, because the tasks arenāt actually dependent and shouldnāt block each other, and subtasks are also not appropriate since the different tasks often apply to different systems.
This request has more votes and activity than some of the requests that are being considered by Asana. Iām not a developer myself but this seems like a simple enough request. Very curious why it keeps getting sidelined for other requests that arenāt as popular.
Since you mentioned a developer vendor, you may be interested in this which was posted today:
Thanks,
Larry
Indeed, @lpb , this feature seems to be coming soon, but Iām hesitant to believe it will be executed in the form Iām suggesting in the OP. It appears it will be a field that you can add various objects, similarly to how the tag field is a āpoolā of labels. However, here it appears we will be able to choose whether it will reference tasks or projects or portfolios or goals.
Although the post you referenced does mention the ability to ācreate structured relationshipsā, I doubt we will have a reference field that we can truly format to contain dropdown options from a list of tasks from a specific project or a list of projects from a specific portfolio, as I am requesting in the OP.
I hope I am wrong - weāll have to wait to see it within the UI, once released.
@Richard_Sather, my post was in response to Lindayās much more than to your OP. The new feature certainly wouldnāt address your request directly.
Thanks,
Larry
Unfortunately Iām not sure this is a solution for my need. Our vendor is not in Asana. Weāre also not using the API and are unable to even use integrations due to some frustrating political rules in our organization. Hopefully this is a solution for other orgs.
The post in the API section was just an early notice to developers that the feature is coming. It will be available in the Asana web app to all users and wonāt need anything related to the API for a user to use it.
An Asana Group PM Lead here - while I donāt own this feature, Reference custom fields are in fact in active development and will be shipped in the coming 1-2 months. Hold us accountable after it ships by sharing your feedback!
@Forum-team, Want to tag appropriately? Thanks!
Hi everyone, Iām excited to announce we are rolling out Reference custom fields!
please find more details in our announcement:
If you have any questions or feedback, please feel free to comment on the announcement post. We will be sharing all your comments directly with our product team!
Hi @Emily_Roman , really excited to see this too.
However, for the reasons I mention in this post could we please keep this thread open for voting and potentially mark as considered instead?
Thanks ![]()
@Richard_Sather I think you should make a new topic that specifically requests the backlinking capability; I just think that concept which youāre asking for is going to get lost in the whole thread of the feature itself being released. (Plus they did release what they planned to, so it seems it should be marked as Launched.)