PLEASE go back to how it was. This is a huge step back for Asana tasks. There isn’t a single workflow or employee in our company that could find this beneficial or easier to use. It prevents us from seeing where and HOW tasks are multihomed in other projects to know exactly how to proceed.
12 Likes
PLEASE undo this!
5 Likes
This is not helping our organization in any way. It is making it harder to handle tasks that are multihomed. Can this type of view be optional? It is making our work less efficient.
6 Likes
I work with Laura Flessner and was just affected today. I work in multiple projects daily and this significant change causes confusion. If this were an optional feature I could be on board, only for the fact we can disable it.
1 Like
Is there a way for a user to go back to their original view of a task?
6 Likes
I’m having a new issue where some of the custom fields I need to see at a glance are hidden automatically in a task. And if a task is across multiple projects, those fields for other projects I need to see at the simultaneously are automatically collapsed/hidden. Is there a setting to toggle on or off the automatic hiding/collapsing of fields in a task? It’s causing our staff to miss some important pieces of information for each task now.
3 Likes
Hi @Carolyn_Collons , welcome to the forum 
What you are experiencing is part of an ongoing A/B test (meaning some users see the new design, while others see the legacy design). I have merged your post into this existing thread to consolidate feedback, where you may also scroll to the top of this thread to vote on whether this A/B test needs further iterations.
1 Like
Hello! It looks like this specific part in Asana changed this morning. Is there a way we can revert it to the previous version? We prefer the old one.
4 Likes
Hi @Ciara_Sabud,
I’ve merged your post with an existing thread on this topic. You can add your vote at the top of the thread.
My Asana was involuntarily updated to this new setup yesterday. I’m really disappointed with the new changes to project views in Asana. The updated sorting and field layout have made something that used to be simple feel unnecessarily clunky. On top of that, shared fields are now showing up as duplicates across projects, creating visual clutter and making it harder to focus on what actually matters. Having to click multiple times just to see the key fields for each task is slowing down my workflow instead of helping it.
What makes this even more frustrating is that it seems I’m the only one in my office who’s been switched to this new setup. Everyone else still has the older, far more efficient layout, which just adds to the confusion.
At the very least, make these new view and sorting changes optional so users can choose the layout that actually works for them. The previous setup was efficient, predictable, and easy to navigate. These new changes feel like a step backward, not an improvement.
Please tell me how I can change my setup to the older view.
2 Likes
The current implementation falls short of this when people have to click see more over and over again when fields live in multiple projects. And what is the true origin of a field when it exists in multiple projects?
Suggestion: Don’t abstract important information behind toggles and don’t assume the system’s logic knows what’s important and what isn’t. Anything that requires additional click directly conflicts with “at a glance.”
The current implementation definitely does not reduce my cognitive overload. I am now seeing redundant fields across every dropdown with no clear indicator which fields are unique to which projects in relation to the selected task’s other fields.
Now I have to scan more information than before due to the redundancy created while trying to mentally figure out which field data is unique based on the context I am in.
I’m normally pretty good with ingesting a ton of information. But this implementation doesn’t seem to be compatible with my flavor of ADHD because I’m effectively been at a standstill for the past four hours unable to get anything done.
More information doesn’t give me cognitive overload. Poor display of information does.
Suggestion:
- Combine fields that exist across more than one of the associated projects into a single table and display that table, in its entirely, without requiring users to click “see more” to see what they want to see.
- Display fields unique to the project that are not already displayed in the combined field view as the first set of fields in the project group.
This adds friction to collaboration for us. Not sure about everyone else.
For us, the current implementation creates noise at a rate that increases with each additional project the task gets multihomed in now. To make up for the fact that the information we need isn’t displayed by default I’m currently going through and adding all custom fields to all projects tasks get multihomed in and ensuring the order is the same, just so we don’t have to guess which project dropdown the field we’re looking for will be in and in what order.
I realize we can’t opt out of this test, but this is the first time in years I’m faced with having to explore alternatives because I don’t know if Asana will be an effective tool for collaboration and getting work done anymore.
9 Likes
Hi @Peyton_Lee Some of my team members are experiencing this change due to the A/B test. And this new layout isn’t useful for our team and will make work more confusing. Since each of our tasks go through a set workflow each day, following the sequence of the custom fields makes things smooth and autonomous for our team. Can this feature be set as optional and not mandatory?
And is there a way to be excluded from this A/B test?
2 Likes
@Peyton_Lee The recent change that collapses all custom fields by project has significantly impacted our workflow. Previously, key custom fields were visible at a glance, allowing us to quickly assess the status and details of tasks. With the new collapsed format, I now have to perform multiple clicks to reveal information that was once immediately accessible.
This change has increased the mental load required to manage tasks effectively and has added extra time to routine project management activities. It has also hidden critical information from the people doing the work, making it more difficult for them to locate key visual indicators that inform their decisions and next steps.
For workflows that rely heavily on custom fields, this update reduces efficiency and creates friction. I strongly recommend reverting this change or, at minimum, providing users with a toggle that allows custom fields to remain expanded by default. Having control over this behavior is essential for teams who depend on rapid, at-a-glance visibility.
7 Likes
I agree, our Project managers in our company that are experiencing this are livid.
My team in IT wasted several hours trying to figure out a solution to help them. This is slowing them down, and it’s adding work onto our plate as tickets come in about this change that they think is a bug.
Asana, please undo this feature. Each click is wasting human time. Especially when it comes to large, multi-departmental projects.
If this feature has to roll out, please enable a feature to auto-expand and let the user choose which one to use. Do not force it upon them.
We pay for your product for us to be more efficient, not less.
8 Likes
This has not been a helpful update. Please provide users the option to opt-in to this view change if it works for their workflows. This has caused more difficulties for how our teams utilize Asana.
3 Likes
Thank you for the context. For me, the way my organizations organizes tasks and projects made this new view significantly INCREASE the cognitive load. Instead of seeing one set of fields, I now have two or three sets of fields that must be expanded to see all of the information relevant to my portion of the task and project.
Because we work by task, having both the project and task show up is confusing and difficult to navigate.
4 Likes
I think this should be a standard in ANY new rollout, at least for the first 6 months to a year of a new feature; especially one of such importance as project management! I understand and appreciate that we’re attempting a more streamlined approach, and there are some ways in which I can see how this could be of benefit, but ultimately, it has significantly increased the number of clicks per task I have to perform, and greatly reduced my overview of a project. I would much prefer an option to default to collapsed or expanded!
2 Likes
Hey Peyton_Lee, the context you provided makes a lot of sense and if we set up all of our workflows with this understanding and design capability in mind, I can see how this view would be superior; however, current state is our organization did not know this was coming and it impacts 20% or so of our users. Because our workflows aren’t set up with this in mind, the structural changes that are required to make this change truly as effective as intended are significant.
When will the A/B test conclude? As a Project Manager, I operate in tasks organization wide that span multiple projects and if this change stays active for more than 60 days I will need to update the structure and set up of my workflows to preserve productivity in spite of this change.
Thank you for the communication and thinking behind this change; I’d love to be apart of the innovations you are trying to drive for Asana users, but doing so knowingly and with forewarning would help immensely.
1 Like
Thank you for sharing the background and explaining why this change is happening. I’m sure that for some teams and organizations, this update is helpful and streamlines their workflows. Unfortunately, I think a large number of us are finding the change time‑consuming, difficult to navigate, or simply not very helpful.
The change doesn’t make sense for how our organization is using Asana, and I’m concerned about how this will affect our less frequent users. They’re already at a disadvantage when it comes to using the software, and they’ll have far less time to adapt to the new experience compared to those of us who work with it every day.
It would be really helpful if this feature were something that users or organizations could choose to turn on or off.
1 Like
Wow. This is a major change and completely changes the way we use ASANA as we update the fields within the task and usually update multiple fields at one time that appear in all different projects so this is going to make a huge amount of extra work trying to find the fields we need to update each time.
3 Likes