Rename Team to Organization
complete
N
Nick Shel
I think it would make a lot of sense to rename Teams to Organizations. That certainly seems more the appropriate word for how the functionality has been built where Organization are really largely independent of each other.
I would then suggest actually creating a concept of real teams within the organization also where by one person could be a member of multiple teams but perhaps have a default team.
This change would remove the confusion and lots of change requests asking to see tasks across the top-level constructs. Although some people may for example want to see their Personal and Work tasks together (perhaps also across multiple organizations they work in) it's far less likely.
Log In
Brendan W
complete
We're closing this request as it's actually been completed a long time ago!
Teams used to be the name of our Workspaces!
Layla at ProcessDriven
In case anyone else is reading this and confused, I believe this request was already partially completed, just not marked so here.
Teams now refer to another part of the hierarchy (group assignees) and "Team" is now "Workspace".
V
Victoria
In complete agreement with renaming Teams to Organizations. The terminology is very confusing.
Greg Treece
Glad to see this is marked as planned. The lack of organization/company/department/team structure is limiting. Favorites helps, but to have a Clickup environment where multiple companies and shared services, all with their own departments and teams can exist, share and collaborate, is very cumbersome currently.
Jenipur Wapaño
This is how we use ClickUp as well. We use Team as one organization and the Spaces as different teams.
Zeb
planned
T
Tarun Masani
Merged in a post:
Sub-Teams or Organisations
N
Nick Shel
They way ClickUp current has the setup is Team is the highest level and there isn't any other grouping of people below that. This makes it difficult to do planning where at an early stage tasks are associated with a particular team rather than an individual and are then assigned to a particular individual within the team at a later stage.
I would suggest that the highest level should probably be called Organization rather than Team. Then it should be possible to define teams of people within that. Alternatively if "Team" is kept perhaps the groupings of people should be called "sub-teams". I would however say that "Organization" is most appropriate at the highest level of the hierarchy.
It's also worth noting that Groups of People (i.e. Teams) within an Organisation often work across projects so it's something that should be defined within the Organization and then used across projects.
A good example of how the concept can work is Portfolio for Jira. Obviously it doesn't need to be as complex, but would be handy.
In the short term obviously Tags can be used to signify a team (without info on who's in it).