@Phil_Seeman , but that is what the OP here is describing.
It is not describing what is being launched with the Reference field MVP and what others are discussing in this thread. Thatās why I donāt think itās beneficial to start a new thread and startover the vote count. Does that make sense?
1 Like
I donāt agree, that would mean creating a new feature requests (and start gathering votes over again) each time a small part of a request is released. The original post is quite specific in envisioning an outcome, which is not achieved with the current release.
It would have been easier if the topic were split up in different topics, but it is a bit hard when youāre envisioning a certain outcome with a lot of related ideas. So I feel there should be a place for requests that are a bit bigger than just changing one thing.
@Forum-team I think this is another argument for allowing a āsolutionā to be selected in English Forum > Product Feedback outside of launched , as this does seem a noteworthy step that deserves a spotlight.
2 Likes
Oh sorry @Richard_Sather, I got confused between this thread and their announcement of the feature release. Asana did release what they planned to for the feature, but not what you asked for in the OP of this thread, so I agree that this thread shouldnāt be marked as Launched.
3 Likes
Thanks, @Phil_Seeman and for @Jan-Rienk weighing in!
Waiting for @Emily_Roman (or someone from @Forum-team) to unmark as launched and perhaps mark as considered instead.
Thanks!
1 Like
@Richard_Sather I just moved the topic back to English Forum > Product Feedback, can you just try to update the title to add what makes it different? Just so itās clear the request is not only for the ability to have a reference custom field 
Thanks!
4 Likes
Thanks, @Emily_Roman . Iāve updated the title to make it more specific and added a PS note at the top of the original post to clarify the difference.
3 Likes
A post was merged into an existing topic: 
Introducing Reference custom fields!
+1 great proposal that will upgrade Asanaās capabilities.
1 Like
Can someone clarify how reference fieldās two-way syncing should work? Iām expecting it work similar to Airtable in that if I edit Task Aās Ref field tagging Task B, then when I go look at Task Bās Ref Field, Task A should appear automatically in that cell.
Is it actually just one-way?
My query is pulling from something Iām trying to figure out in my system, if it doesnāt work as 2-way then Iāll need to figure out a new plan for batches/sprints. Iāll note, these tasks are within the same project, but appear in different filtered Lists based on different task types (Task vs. Content).
1 Like
Hi @Leslie_Montgomery , welcome to the forum 
Unfortunately, the current Reference field feature only supports one-way linking. Thus the reason why this thread still stands, for you and others to vote on.
The good news is that it is being considered with the hope that it will go into in-development sometime soon.
1 Like
New to the forum as we are about to start using Asana. Would love for the bi-directional Reference fields, similar to how it can be set up in Notion.
Our plan is to have a āLive Sessionā task link to a āTopicsā task so we can track when we presented on specific topics to our teams. One-way linking will be fine for now, but would 100% love auto-bidrectional linking.
1 Like
Fortunately, filtering objects is now possible for reference fields but it still has a few limitations. For instance, you can select tasks only within a specific project but you canāt specify whether subtasks should also be included even though they arenāt part of the project itself. This would be incredibly helpful to us.
So I hope this option is also planned for another feature update.
2 Likes
Hi @Cyrill , it seems like @Arthur_BEGOU also had the same idea, today!
Make sure to vote!
3 Likes