It's essential for our workflow to organize projects into folders. I assumed Organizations worked like folders, but clearly that's not what they're designed for.
So we really need a way to organize projects within an Organization, and then assign a Member access to a specific folder, instead of the whole organization or individual projects.
The whole Workspace, Organization structure is confusing. It seems like an Organization would have mutliple Workspaces comprised of multiple Projects. Really the concept is people work in teams. I think Organizations should be called Teams and placed above Workspace. Each Team, which can have one or more members, would have one or more Workspaces, that would each comprise of one or more related Projects. That makes more sense to me conceptually.
Lane Smith, Jun 2, 2021
Yes it's quite confusing, what you also need to consider is each organization will need it's own separate paid plan when they are released. Which is why folders within an Organization makes sense, or there is no way to group/organize your projects.
In your example a "Workspace" would act like a "Folder". It really doesn't matter what they're called, as long as I can group projects without paying for extra organizations.
Serge, Jun 3, 2021
Hi Serge and Lance - I will pass your suggestions to our team and keep you posted if we have any updates.
For the feedback about the names for Workspaces, I will also bring it to the team for more discussion. We named it the 'Workspace' because we are referring to the entire main panel and the detail panel on the right hand side. Under Workspace, you can find Organizations and Projects. Clicking on each organization or project, the right hand side will change accordingly. Here's a guide explaining more about the hierarchy inside Quire: https://quire.io/guide/organization-project-task/. I hope this helps. Thanks!
Peggy, Jun 3, 2021
@peggy Thanks, Peggy. The link you provided is helpful and the hierarchy makes sense. However, I would use different terminology. The main one calling organizations teams instead. I think that is the standard term in the industry. Each Organization (or Team) has many projects it works on and each Project has many tasks. As to what Serge is referring to for folders to group projects seems like a request for another level between Organization and Project. Like perhaps Project and Sub-project. Similar to Tasks and Sub-tasks. I guess some folks might find that useful. It would need to be a toggle for those who don't need it. But projects can be grouped by Organization that you can mix and match members. Maybe the hierarchy could be like this: Workspace>Organization(s)>Team(s)>Project(s)>Tasks
Lane Smith, Jun 3, 2021
Lane, I think you are missing the key point. Each organization has a separate monthly fee PER member. Otherwise I could use organizations for simply grouping projects. So the use/purpose of Organizations is clearly much broader than grouping. Which is why another level just for grouping/organizing projects is needed.
As it currently stands, if I want to organize my projects into 10 groups/folders, I would essentially be paying 10X just for "folders"...
Serge, Jun 3, 2021