So to clarify, when I look at the Projects in the Breadcrumb, they appear to be nested; however, the search/browse Projects doesn't reflect taxonomy...and the concept of "Moving a Project" doesn't exist anywhere in the admin/action menu. Hence my comments about it being perceived as "flat". While not 100% accurate, those were my observations, but given the breadcrumb there does appear to be a nested element to them...just thought I'd correct myself before some else did. =)
Thanks for the feedback on Projects! You bring up several great improvement areas, most of which we're addressing in the next release.
It is really interesting to hear about your perception of how Projects are hierarchical/flat. They are hierarchical, but clearly we missed on expressing that in the global list of Projects.
So I'm confused... Projects are hierarchical in 2.5?
It seems like projects have no way to be archived, and what's more... no way to be nested.
I think it's important to reflect Agile methodologies in the project tool - which is to say 1 project should be able to contain several smaller projects working in tandem, and it should be intuitive to different users. For instance Windows and Networking should view only the nested projects pertinent to them, but the manager of the project should be able to see the status of both teams on 1 calendar in different colors. The health of the various projects would then derive the health of the overall larger project. This allows granularity for teams and archiving for documentation, but also allows identifying points of failure without having to establish dependencies like waterfall methodology.
Is this essentially already in Clearspace and I'm just a n00b?