We have a big “project” that shows an overview of all current projects (all project tasks are being multihomed here). I would like to be able to create a dashboard that breaks down information by project. However, “project” is not one of the available filters in the widgets. Are there any workarounds for this, except creating an additional special field called “project” on the individual project tiles? I understand portfolios include similar functionality but they are not available to us right now.
If I understand correctly, you can do this with Universal Reporting (Reporting in the sidebar) by specifying the big project and one other project in each chart and looking at the charts side-by-side. This feature is available in any paid plan (where as portfolios requires Advanced and above.
Thanks,
Larry
PS Don’t forget to click the title to scroll to the top and vote by clicking the Vote button; that’s the quickest and most effective way to express your support for a request.
Thank you so much for including that link! There’s some helpful information in there. The issue I’m running into is that I’m not getting “project” as an option in my X-axis. I basically had to create a special field on every project called “project” and I’m able to get it on the X-axis by selecting that special field. However, that seems quite duplicative. Any thoughts on why this is happening?
With that information, and re-reading your initial request, I realize that you’re representing projects as tasks (right?)? And those tasks are multi-homed to the “big” project-of-projects and to the actual project, if I understand. Dashboards are not set up for that–they’re not able to disambiguate that one is a “real” project and the other is the “collector” project.
If you’re on an Enterprise plan you could likely use a script action to maintain that project custom field so you don’t have to do it manually.
But the underlying issue is: If you put those projects in a portfolio (Advanced and above plans) then you’d be able to have project as an X-axis choice.
PS This won’t help, I don’t think, but I actually had a similar need in Asana2Go (Disclaimer: I’m the creator) so I’ve seen that issue, but I was able to address it in the scripting language I used to implement: