I would like to add individual tasks to a Portfolio alongside Projects.
My team manages a large number of small projects (2-5 tasks), and we have found creating projects for these difficult to manage - we would end up with a hundred projects and I don’t think Asana is really designed for this.
For these small projects we would like to use a Tasks/Subtasks hierarchy rather than Project/Task. But we are also using Portfolios to track project focus for various stakeholders and the two don’t mix - we can only add Projects to Portfolios, not individual tasks.
This would be great! My team would find this highly beneficial. I also would love to have the option to add the entirety of someone’s “My Tasks” to a portfolio. Currently, I oversee my team’s workflow by having them manage their tasks in individual projects, allowing me to view their bandwidth within a portfolio synced to their projects. However, I’d much rather scratch individual projects and let my crew stick to “My Tasks” so we don’t have to unnecessarily create and manage projects just to have task lists I can view.
I’d also like to see the ability to manage tasks on the Portfolio level. We have multiple features (Projects) that roll up into a Quarterly Release (Portfolio). Some tasks, like communications span across each of the projects. Instead of repeating the same tasks on every project, I’d rather have one that just lives on the Portfolio.
Please add this as mentioned. We have a mix of small and large projects that we need to see all at once, and like an earlier poster mentioned, we would have upwards of hundreds of projects to manage which is not well supported in Asana work flow.
This would be monumental in our organization. Marketing classifies departments as “Projects” with all the small jobs in that “project/team” listed as tasks. This is the old “job jacket” style that is still popular with many agencies. The other departments outside of Marketing use Asana the way Asana wants to be used… by creating Projects for each and every job (EXTREMELY cluttered). While projects are great for reporting up to management – they’re not good for the user who wants to see a complete view of all their projects (“tasks”) in a single view. This needs to be a top feature priority, since not all people work the same. Anyone coming from Microsoft Planner, or HIVE, etc., will run a high chance of wanting to use the board/job jacket style.