Copying/duplicating project instead of being moved

[Bryan_TeamKickstart]

@Jon_Glendinning - This has been a common confusion with a recent feature change.
Let me explain.

It’s not “copying” it to the 2nd team. It’s sharing it. So, don’t delete it from the first team after “moving” the project. Instead, go to the Share button in the project, and remove the permissions from the 1st team.

If you want to read more about this discussion and the details from the Asana team, you can read more here:

About team sharing, project membership in team(s), and also free plans

Hi @Vanessa_N, Thank you for your response. I would still appreciate your perspective on this: It sounds odd that when you change the team in Project settings it woud add a team instead. Regardless of what plan people are on. What I’ve tested in my Phoenix instance results in another behaviour, is that it changes the location of which project the team lives, but it doesn’t change any access settings. So while I’ve changed the team, the new team doesn’t have access to the project as “shared …

And, if you’d like to vote for improvements to the process of moving a project to another team, please vote here:

Improve the moving of projects

With the introduction of Team sharing the default behaviour for changing the team in the project settings has changed. Instead of moving the project to another team (what is logical to suspect when you change a setting that can only contain one team) it doesn’t change the team, but rather adds another team. EDIT: I was wrong about this. Changing the team through project settings only changes where the team lives. It does not change who can access the team. This is leading to confusion: I’m …