We are getting the “Weekly portfolio report” from Asana shared via email. What I saw that it the weekly report shows projects which have been completed for a long time. I cannot find the settings / configuration to limit the “Weekly portfolio report” only showing the running projects.
The report shows indeed the project I have access to, but the report shows also completed and archived projects. And I would expect that the “weekly portfolio report” does not share information about projects that are completed or even archived. But, it remains unclear where I can configure what is part of that weekly portfolio report.
Hi @Niels_Oomen , indeed there isn’t any setting to customize the weekly email. However, if you set a filter to your portfolio’s List view, to exclude archived projects, as @Jan-Rienk suggested, perhaps that will affect the contents of the weekly email.
I will give you an update, but I already know that filtering does not work. Because this is what I have done before. I had 44 project (including some archived + completed). I have removed the archived projects form the portfolio, so that reduces the list to 26 project. However, we have 14 running projects so, I expect that they other 12 also will be on the list.
Jumping back to this topic in February 2026. I noticed the same issue mentioned above. I received a “Weekly Portfolio Report” email, and it includes a section for “Work without recent updates,” and almost all of those projects listed are projects that are already marked as Complete and have been archived. Some for MONTHS. Is there a fix for only listing active, incomplete projects in the “Weekly Portfolio Report” email?
I think it would be great if Asana would only send weekly email report on projects in a portfolio that are still open. As it is now, it is not helpful, and actually adds work, because I have to sift through a long list of projects that are closed/completed to get to the ones that are truly open and need status updates.
Archived projects or those having Status = Complete are only relevant for a short time to communicate the end of the project life cycle. Acknowledging PMO’s do retain a project’s association with a portfolio for lots of reasons - reporting, end of year retrospective, etc. But there is no reason why an old, retired project would need a status update just because it is connected to a Portfolio.
Consider developing features that adhere to the project owner’s intentions to archive the project and make archived projects omitted or filterable from more places projects are shown, like this email.