Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Disable the Copy Project feature


Level 2


We have seen many issues with copied projects that lead to incorrect/missing tasks, assignments, irrelevant documents getting carried over etc to name a few.

Disabling the copy feature would help ensure all the projects created in Workfront are in sync with the latest enhancements and updates that are in place.



Level 2


Challenges the native copy feature causes:

  • Risk issue- We have about ~25 standard project templates that only our sys admin team manages changes. Copied projects do not leverage the latest template but instead open the door for using older versions of our standard project templates. This is an open risk for staying compliant with set standards. For example, new tasks and/or custom forms that are meant to validate a process may not be accounted for on project created via the native copy process. We make new risk control improvements every internal release and the effectiveness of these updates are dependent on using the latest templates.

  • Downstream issues-
    • Task Assignments- today the native feature only allows for using existing assignments or clearing assignments on the original project. There isn’t an option to update the copied version with just the pre-defined task assigned job roles, which is what our users expected to happen when they select “clear assignments”. So they are left with either blank assignments, no sense of job role to staff or incorrect user names that aren’t relevant to the new project.
    • Launch dates- in a new request our current automation takes the “launch date” field entered and updates a launch date task on the standard project template. All tasks dates are connected to this launch date task and our automation recalculates the timeline. All downstream teams can trust the new tasks on their dashboards are accurate. Using the copy feature, this is a manual step to update the request launch date AND the project launch task AND the project timeline (which does not happen or not in a timely manner)


Level 3


I would like the ability to disable the Copy Project feature as well. Our templates have changed and many of the tasks and assignments are incorrect on older projects. Also we have an API numbering app that doesn't automatically assign project numbers on copied projects. And honestly I don't think it saves any time for the project owner because of all of the updates needed for a copied project.


Level 10



Now make disable as a System Administrator setting - I'd agree with.



Level 9


Agreed with other comments in that we don't want to completely remove the copying feature, but we, as Admins, would like control over disabling it if need be (user, team, or group levels would be great).


Level 10


I too completely disagree in this regard, there might be few option can be added while copying such as;

1) Add Excluding few features (predecessors / assignments / planned hours etc.). Since when we create any project best to refer the template. Also keep control and review periodically.

2) Agree with @Nick Valeriote, can be added to control from system admin point of view would be also good.