Include Sections when Search results are sorted by Project


I appreciate the response! However, this doesn’t work well for us for a few reasons:

  • The print view still works as we would expect, so it creates yet another level of discontinuity for our team.
  • While sections do contain tasks, we really need them to behave as a section in the sense that it contains tasks and creates actual sections for them within projects. To be able to sort them in project view this way is wonderful, but to not be able to see that reflected in an organization or management-wide view of projects is frustrating and breaks what I believe is the intent for them. We use sections to separate phases (in a project), task types (in an office management type “project”), etc. Creating custom fields does not provide the appropriate level of separation, and creates a task that is now redundant, as we will still need to assign sections for future board-to-list functionality.

We are paying customers, but I would imagine anyone with a free version would not be satisfied with a custom field workaround for something that I feel is an intuitive use for sections (assuming custom fields are still a paid-only feature). Please consider changing this. I was so excited about the coming changes to sections until realizing this aspect was not considered a bug after all.

1 Like

Agree. If this is permanent, sections have become a redundant step to accommodate swapping to board view in the future at the expense of list view functionality.


Is there any plan to address this? We implemented Asana at my company about 8 months ago largely due to the functionality of being able to quickly develop a single organized report across multiple projects. This change breaks workflow for our entire company with seemingly zero benefit, which is a massive deterrent to continuing use of this tool


Briefly describe (1-2 sentences) the Bug you’re experiencing:

Steps to reproduce: i’m not sure how you name this feature. it’s a task with an":" at the end to structure projects. our problem is that we strongly depend on a project overview. therefore we created a meta project named “projectupdate” and tagged each task of each project with the tag"projectupdate. the problem is that you guys made an update in the last few days/weeks so the feature “Headline with : & underline” is only shown in projects but not the one based on tags…this is bad for us and we strongly depend on this feature! please let me know if this is a bug (which will be changed) or a feature (will stay as it is).

FYI, we’re premium customer

Browser version: any

Upload screenshots below:



Hey @Niklas_Strohmeier, welcome to the Asana Community Forum!

Thank you for taking the time to share this with us, I have tested this on my end and was able to reproduce exactly what you are experiencing and showing in your screenshots.

I was also able to find an existing thread on the same topic in the #productfeedback category and have merged yours into it to allow other Forum members to easily find it and vote for it, I hope you don’t mind!


It’s true, in the print view it shows, haven’t noted it before.

I see this as a functionality drop, or bug, that also affects my main use of asana. In my case I need to filter tasks from a project, showing them ordered by sections, as they were manually put there.


To add to what others have said here, this is an issue for my team as well. @Marie this impacts every one of our projects. We use sections and we need to be able to search across projects and have sections display.

I don’t understand why the intended result of this change is to remove functionality that paying customers are using without providing an alternative.

The custom field workaround will not work for us as we have 75+ sections across our projects. Like others have said, you cannot filter a serach by a custom field and only the first few characters of the field are shown on a search. Not helpful. We need the ability to sort tasks in a search based on sections.

I continue to be frustrated by the suggestions that are shared on this forum that never get implemented. It only makes matters worse when features we rely on are taken away. These are your most engaged users and your team should listen to them.