There are definitely more people complaining about how this works than like it. That said, this is just what we see in the forums. It’s definitely not a representative sample and definitely not a random sample.
No clue what their internal data is showing across usage…but I do hope they revisit and iterate on this soon. I have about 4 months left on my annual contract but have already started using an alternative more and more because of this change.
Our team uses a large number of custom fields, which we manage through a “Mega Board.” We also house many of our rules there. This setup has helped ensure every task contains the necessary fields and automations since all tasks must live in the Mega Board.
However, after a recent Asana update, users can now see every project a task belongs to along with all associated custom fields. This has created some confusion for our team and has made the fields feel more overwhelming than they actually are.
I’m not sure if this update has impacted other teams’ workflows as well, but the previous view of the fields was helpful where it was combined into one list.
Hi @Taylor_Giddens,
FYI I merged your post with an existing thread on this topic. Be sure to add your vote at the top of the thread.
I would love to see how other people have leveled up their workflows because of this change. Could you share the alternative’s you have used?
Great, I guess this will be the new appearance of Asana.
Honestly, I also don’t understand who it helps to see all the fields from the parent, especially since there are rules that let you make the subtask inherit only the fields it actually needs from the parent. Especially if you have a lot of fields, you end up spending a long time trying to find the information you actually need.
WOW this feature has gone from BAD to worse. Not only does it NOT merge like it used to (inherited fields added to ONE section instead of 4 sections for each project) NOW… it also shows the project that the PARENT task is on. BUT WAIT, you can’t actually do anything with that (like change the section of the project). You have to go in and RE-ADD the project, and then you can edit the section, etc.
Asana used to really work well for us but this feature frustrates me. We had things set up in a way that worked, and we want to opt out of this new crummy features.
PLEASSEEEEE we need the old version!!! Consolidated fields was just so much more helpful than this chaotic duplication drama
It would be nice to get a straight answer here:
a) “We heard you, and we will do something about it,”
b) “We think the UI changes are better and we will not change them”
The current state doesn’t work with our old workflow (and other teams who spoke out in this thread)
But without closure, we are not sure if we should overhaul everything, patiently wait for the ability to revert, or look for an alternative that can give us what we had with the old UI
Can we have an option to toggle this off and continue using the previous view?
If this new layout is benefiting some users, that’s great, but for our team it creates significant information overload. We work across many cross-functional projects, so having all project and custom field information surfaced in this way makes tasks much harder to scan and navigate efficiently.
Also, is there any update on progress regarding this feedback?
To follow on from my last post, here is how are tasks looking when unpopulated. Super overwhelming and lots of visual noise. Important details are getting lost amongst project names, custom fields and metadata that aren’t always relevant in the moment.
If this feature isn’t going to be rolled back, does anyone have any recommendations or best practices for reducing the clutter? I’m interested to hear how other organisations with large numbers of cross-functional projects are managing this, as the current experience is proving quite challenging for our team.
Hey @Phil_Seeman ! Has there been in development in this being changed? It seems that this has frustrated many people and disrupted many workflows.
Hi @Taylor_Giddens,
I don’t work for Asana so I don’t know the answer to that question, sorry. I know they are discussing it internally. @Stef_O any chance you have an update to share?
Sorry about that @Phil_Seeman ! I got it mixed up since you are a Forum Leader.
@Stef_O An update would be appreciated!
