Good news: This change that I requested about a month ago just appeared today in my org:
Thanks for listening, @Peyton_Lee and team!
Larry
PS Be careful of that “x” at the far right:
1 Like
Well, after a full day of using this new layout I can confidently say I hope it fails the A/B test and goes through several major iterations before ever seeing general access/rollout.
- The redundancy across projects increases noise. I recognize I could change the order of fields in these other projects, but that still doesn’t give me all the information I need across all contexts in which the item lives at once.
- I have zero desire to click Show
xmore over and over again throughout the day to then have to decipher what I’m looking at.
I want maximum context, information density, with minimal redundancy.
I get that this treatment was done with the hope that it would allow users to increase the number of fields they can display in a task pane while also reducing load times—hence why each project dropdown is limited to ≈5 fields by default.
However, I don’t see how this is going to improve UX with respect to total fields displayed and load time when some users are still going to have to click on the “Show
xmore” option for each project…if anything, it seems like it would increase the overall load.
Workaround I’m Considering:
A workaround I have in mind currently is to write a script to automatically expand each Project list’s fields since they aren’t automatically loaded in the DOM, identify each custom field’s ID from the TaskPaneFields-customFieldTables element, then check for and remove duplicates. And finally, reconstruct the more useful layout by consolidating all fields back into a single panel like they were before.
6 Likes
This change has come to my environment.
In my opinion, it’s too bad. It’s confusing me.
I can understand that someone wants to know where fields come from.
But it’s not often, I guess.
So I hope we can switch appearances, such as ‘by projects’ or ‘by nothing’.
4 Likes
For us also: the new layout hides releveant task information from the user and will result in several thousand extra klicks daily for our teams to see what they need to. We use most custom fields in all projects, so the change doesn’t improve anything for the way we work with Asana, just creates more workload.
3 Likes
I agree. Collapsing which projects a task is associated with (and thus its custom fields) is a huge step backwards in terms of efficiency.
I operate mainly out of My Tasks view and to have to
- click a super tiny drop down arrow
- then scroll to find my timer,
- then click start timer just to record my time (this is very annoying.
It’s even more annoying when your working from a subtask and you have add another click to “show inherited fields” then click the microscopic drop down arrow, etc.
Please revert to prior view! Thanks for your time and consideration.
2 Likes
I agree with everyone on this thread. The new view is highly disturbing and makes people’s work more difficult.
We have several multihomed tasks, but not everyone is on all the projects. They will miss crucial fields in this collapsed and separated by default function.
I’d suggest the Asana team to see how Notion handles these. As it’d be highly valueble if there was an option to change the order in which the Projects appear custom fields appear; pin some fields for example so it’d appear in every view.
There are dozens of custom fields and only a few relevant to most teams, while the rest is for admin/ ops and the unability to hide these already makes the most teams’ views quite noisy.
If this is not improved, we’d rather have the old version back, please and thank you.
3 Likes
This has become a huge nuisance for our team as well. We went from having all information at a glance, to having collapse-expand sections where we are forced to hunt down specific information. Having all the fields available at a glance, and with no repetition (Status Update, etc.) was a big factor in our efficiency. We’re in and out of dozens of tasks everyday, and the update has limited that efficiency and increased frustration for everyone.
5 Likes
Completely on board with all of your points here. Thanks for taking the time to communicate your reasoning
1 Like
For anyone looking to go back to the older view: Asana support was able to revert my account to the previous version after I submitted a ticket.
3 Likes
First, thanks to Asana for trying to improve things. Second, i would like this update rolled back or made optional for all the reasons already shared. Thank you.
3 Likes
Regarding this UI change.
So I think the UI changes are good. I still think some fine-tuning is needed, though.
The reason is that in the previous task details display, if there were a lot of custom fields (Asana’s multi-homing feature allows you to assign tasks to multiple projects), all related custom fields would be displayed, which I found confusing.
In particular, with the recent expansion of custom field functionality, there’s a trend toward an increase in custom fields for individual projects.
Here’s the example I’m having trouble with.
Setting fields for individual projects.
Project A: Fields are “Select1” and “Text1”
Project B: Fields are “Select2” and “Text2”
If Task 1 is multi-homed to Projects A and B,
Fields will be displayed like this:
“Select1”
“Text1”
“Select2”
“Text2”
It’s very confusing.
What’s unfortunate is that Asana conducts A/B testing without any warning. I think the recent announcement, “Introducing Release Preview Console for Enterprise Admins!”, is a countermeasure.
1 Like
This new layout is also causing me issues when setting or updating values for Estimated time and Actual time.
Let’s say I have the Estimated time already set in Project A and attributable to Project A.
Now let’s say I need to adjust that Estimated time while I am viewing the task within in Project B. When I do so, it automatically attributes the time to Project B when I hit Tab after entering the time value because the Project Groups default to expanding the one that it “thinks” is most relevant to the Project I am in.
But that’s not what I want to happen. When I make a change to an existing time value I want it to stay attributable to the project I already had it set to—regardless of what project I am actually in when I make that change.
I can change it after the fact, but now I have to be even more diligent than I was before to make sure things aren’t changing. This is just increasing the potential for mistakes and is going to cause more headaches. I have yet to experience any positive benefit from this feature thus far.
Perhaps we should consider introducing filter, sort, group, and option functionalities, similar to those in the project?
2 Likes
I’ve personally not run into issues with the new UI and for parts I see the benefit.
Some teams in our company work heavily with fields from different projects and these are now hidden under different collapsed projects.
anyway the extra clicks are avoided to expand collapsed custom fields?
or even to add certain custom fields to a projects main task UI (like promoting them or starring them for that particular project) and leave the rest hidden?
Thanks,
Simon
2 Likes
Is there any updates on when we can have the old version back? We prefer the old one as it looks cleaner and efficient. Thanks!
2 Likes
Is there anyway to switch back to the old design this is just adding extra steps to my process and making it more difficult to do my job. I now have extra clicks to find out what projects the task is connected to rather that just seeing them all in one spot. What makes it worse is that my team sees the old and I am stuck on this new view so when I am trying to show them how to do something it doesn’t match. What a bad design!
7 Likes
We’re having the opposite problem. My workspace is still showing the old version, and a large number of our users have been rolled into the test, thus meaning I can’t even test the changes to help troubleshoot how it affects our workflows.
1 Like
Not sure if anyone else has received this update in their Asana where it hides all the custom fields in the tasks and won’t display them unless you click the drop-down of those projects - is there a way to revert to the old display? This is frankly horrendous to look at, but the bigger problem is all of our users are incredibly confused by this new display. They do not find this user friendly to anyone outside of the PM role; the frequent term I hear is “chaotic” (and frankly even the PMs don’t find this user-friendly either). A lot of our users need to fill out portions of these fields while their tasks are in progress and not having them automatically displayed is disorienting for them.
2 Likes
Welcome to the forum @Tatiana_Torres!
You’ve submitted this in product feedback, which gives people the option to vote for the feedback.
Can you describe your ask clearly in the title, so that it is clear what people are voting for?
Also, don’t forget to vote yourself. 
Hi @Tatiana_Torres , I’ve moved your post into this existing thread where your votes have been consolidated, along with all the other feedback.
1 Like