Hierarchy? Dashboard?

Back after a year, now v.2. is launched. I find things pretty confusing.

  • Where do I find and overview of my projects / lists?
  • Do lists contain projects? Huh? How is the hierarchy organized?
  • Can I use folders?

Welcome back, Max :smiley:

  • If you’re referencing a Browse all menu, you can see the full list of objects across Height by opening the Command-K palette (cmd+k) > Type “Browse all” > Select Lists to see the full menu of lists, and type “Projects” in the browse all search bar to see all project views.
  • Project is simply a type of object in Height. With this, you can have tasks and projects, and the distinction is the Type attribute. Projects are indicated by the flag icon next to the project’s name, so any object in Height that has a flag icon, is a project. You can create and add projects to list if you’d like, or you can simply create a new project from the + menu in the sidebar (or team page) to make a project that’s independent of lists. (If you do this, the project will be auto-listed in the Projects view under the selected team.)
  • Folders aren’t supported, but when you create Teams in Height, they’re listed in the sidebar as sections that are similar to folders.

Thank you Akila, your support is great and friendly as always. And I understand the first and third point. But the second?

Height is, if I understand it correctly, a project management app. So, projects are the central entities, right? Not just ‘simply a type of object in Height’ right?

To make a WBS for example, with deliverables on several levels and tasks at its lowest level, It needs clear hierarchical tools. So, I do not understand projects can be a part of lists. I would say a list should be a part of a project.

Maybe the whole nomenclature in Height should be changed?

Our team spent a lot of time trying to understand this thing of “Teams” and “Projects”. Maybe more documentation would be of great help.