The project listing page will need to have organizations factored into the project listings. Below are a few additions for this listing page, however it's important to consider the problems and design considerations:
Almost all users only have a singular organization, so redundantly listing the name of the organization in the project name or inside the project listing is a lot of wasted real estate.
Almost more important to this view would be the organization team, instead of just the organization. However, teams don't own projects, so this isn't a clear case of listing the projects sorted by team.
We can filter on teams though.
Some solutions to the above notes:
Only show the organization in the listing if the user belongs to more than one organization. Is this even worth it? Check the number of users this applies to, it very well might be essentially just the core team.
Having an organization filter might be most useful, instead of working the organization in the listing display. This is an okay middle ground.
Or, skip organization filtering and instead rely on team filtering to imply the organization? Or have a separate "All Foo organization teams"? Or a multi select filter instead? Again, the number of users here would be important.
So, a few feature additions to this page:
[ ] Maybe an organization metadata in the project listing items
[ ] Maybe an organization or team filter in the project listing
[ ] Maybe organization sidebar content? We currently have some links
The project listing page will need to have organizations factored into the project listings. Below are a few additions for this listing page, however it's important to consider the problems and design considerations:
Some solutions to the above notes:
So, a few feature additions to this page: