We are encountering the same problems you mentioned above. There’s another thread about this that I’ve posted in multiple times with the same concerns. I can’t seem to find it right now, but I’m hoping someone else can link to it.
1 Like
I completely agree with this.
The loss of a unified view is particularly challenging in day-to-day work. When a task spans multiple projects, having to navigate into each one just to piece together its full context disrupts the workflow and introduces unnecessary friction.
I also want to reinforce the point about field duplication — in our case, this is not a viable workaround, as fields are intentionally designed to reflect different scopes and responsibilities.
It would be extremely valuable to restore a consolidated view, or at least provide an aggregated layer for multi-project tasks.
2 Likes
Welcome, @Ana_Freire and @Cátia_Marques, and thanks @Jess_deCsesznak
I’ve merged your posts into an existing topic where you can click the title to scroll to the top and vote by clicking the Vote button (which currently doesn’t say “Vote” but it’s the oval with a count under it).
Thanks,
Larry
1 Like
To Asana Staff,
I’d like to hear some feedback from an Asana team lead as to how you’re listening to your user base here. Clearly the community is asking for you to remove this feature. You have within your power the ability to listen to your users and set this back to the way it was. This is clearly not a “growing pain” - this is a true disruption in efficiency and is clearly unnecessary for your users. What steps is Asana working through to hear what we’re saying, and undo this poorly implemented feature?
3 Likes
I don’t remember my dreams often. And when I do, it’s rare that talk about them because it’s kinda boring.
But over the weekend I dreamt I was looking at a task pane and this was somewhat fixed. All the fields every project had in common were consolidated up at the top.
Now, this is the first and only time in my life I’ve thought about Asana while I’m asleep.
I would very much like to never think about Asana while I’m not working, much less while I’m asleep ever again. That’s weird and it can’t be healthy haha.
3 Likes
Adding my voice to this thread — the new grouped-by-project layout in the task detail pane is a step backwards for our team. When a task lives in multiple projects that share custom fields, those fields now appear duplicated in every project section, creating unnecessary visual clutter and making the pane harder to scan quickly. Also there is always a section for My Tasks so even when the task is only assigned to a single project I still see the custom fields duplicated.
We’d strongly prefer an option to revert to the single merged view, or at minimum a toggle that lets users choose their preferred layout. Please consider giving users control over this — the old behavior was cleaner and more efficient for day-to-day task management.
6 Likes
Although this feature update may not yet represent the pinnacle of perfection, I find it to be a marked improvement over its predecessor.
I sincerely hope for further refinements in the future.
Hi
We use Asana for our artwork tasks. Since you have introduced the new way projects are seen, deadlines are sllpping. When you used to go into a task our bespoke fields: status and priority etc would show for both. That way artwork could see if amendments were needed or approvals had been made. Now both teams appear in task but the the drop down menus are collapsed. The old way was a lot easier - you could see that the task was in both teams but only had one set of fields.
This again adds one more step as many of the changes have added.
1 Like
I’ve merged your post into an existing topic where you can click the title to scroll to the top and vote by clicking the Vote button at the top-left.
Thanks,
Larry
1 Like
Just to add a thought here - while I don’t hate the new layout for tasks, one thing that has been lost is the ability to bulk edit ‘custom fields’ within a project (if the fields are not native to that project).
For example, I have a few of my own custom fields I use to manage ‘My Tasks’ page. If I am, say, assigning myself 15 different ‘email deadline’ tasks from my ‘email’ project, all with various dependencies and blocks and deadlines, I used to be able to also update the custom field for all of the tasks at the same time. Now, when I bulk select these tasks, I can only edit the custom fields for that project. I then have to go into My Tasks (or other multi-home project) and find all the tasks and edit the custom field there. Or edit the fields one by one in task view.
Like I said, I don’t mind the new view for custom fields but when I’m selecting bulk tasks, I want the ability to edit the custom fields the tasks are multi-homed in, not just the current project.
2 Likes
Hi ,
We noticed that the subtasks are taking the fields from the project where the parent task is located. Why was this change made? The subtasks are already in their own projects, and if the projects where the parent task is located are also shown, the workflow becomes even more difficult than it already did after the changes you made to the way fields are displayed in tasks.
1 Like
Hi @i.lagou , that shouldn’t happen and I cannot replicate it unless the subtask is in fact added to the project that the parent task is added.
Instead, you should see a blue text ‘Show inherited fields’.
Perhaps you have a rule that is also adding them to the parent task’s project? Please check if that’s thw case, otherwise this could be an A/B test or a bug. Have you reached out to Asana support to investigate?
Hi Richard, this appeared yesterday — it wasn’t like this before. Previously, we were seeing the “Show inherited fields” option. I’ll reach out to Asana support and check with them.
1 Like
I was informed by support that this is now the new default version of Asana moving forward.
When opening a parent task and navigating to a subtask, the first thing displayed is the parent project’s fields already expanded/open, together with the subtask’s own projects. As a result, to access the actual subtask information, we first have to close the parent project fields and then manually open the correct subtask project fields.
This adds unnecessary extra clicks and makes navigation slower and more confusing than before.
@Stef_O , can you please confirm if the above is true? Is it an A/B test or actually rolling out?
1 Like
I guess here is our answer:
I added a response to that post, but wanted to flag a portion of it here as well, since it’s inspired by that change, but also specifically applicable to this conversation:
…it makes far more sense to me to show multi-homed and parent’s project custom field information presented as a table with the projects each field lives in as a column to the right (as it is in list view) rather than as toggle-open categorization by project. That would allow the key information – the contents of the custom fields – to be prioritized over where that information happens to live, and could also potentially eliminate the duplicated fields situation so many people have been struggling with.
Can you clarify what you like about it and how it helps your team? It seems like you may be the outlier here and maybe there’s an important workflow that we’re not seeing - most of us aren’t seeing. So far, this is the first comment in favor that I’ve read. This is why options are important to users.
Hi, @Richard_Parke .
My thoughts are something like this.
Thanks for sharing. I don’t find the previous workflow confusing at all. The reality is that a task is a task, and it has a description of the work to be completed. If it is attached to multiple projects (which we do), I would still want to know everything about that project and it’s associated fields in one place. If you have a lot of fields, that’s a lot of duplicated fields, and all this has done is create so many extra clicks to get to the same thing. This is a perfect example of what Asana should invest in feature-options. Your way isn’t wrong, and neither is mine. Both workflows get the job done in the particular environment that works best for the corresponding team. What works for us, might not work for you - and that’s okay. Asana should recognize this. Teams are not machines made in a factory with the same switches, knobs, and features. Teams are dynamic and the minute you change a person on a team, the entire dynamic shifts. This is something Asana is not seeing when they roll out newn functionalities like this. There are just about as many people complaining about this as there are people who like it - in fact, I’d say it’s much more. 
It’s just something that I think Asana could work on. Thanks for listening and corresponding with me.
1 Like