Once a third-party has modified the server project and sent it back to you, you can update a project on the server using the server project file that you received. To update your project, you need to import the received file to the Teamwork Cloud server as a new version of the project.

Permissions

  • To update a server project from a server project file, you need the Administer Resources permission.
  • To update a main project and used projects with changes from the server project file, you must have read-write permission for all branches requiring updates.

The branch selected for update cannot contain any locks. Locks must be released before updating the project.


To update a server project with changes from a server project file

  1. Do one of the following:
    • Open the server project. In the main menu, click Collaborate > Update from Local Project.
    • In the main menu, click Collaborate > Projects. The Manage Projects dialog opens. Right-click the project you need to update under the Online Projects tab. Then select Update from Local Project.
    • In the main menu, click Collaborate > Projects. The Manage Projects dialog opens. Select the project you need to update and then click .

  2. When the Update from Local Project dialog opens:

    • select the .szip file you want to use to update the server project;

    • specify the branch to update:

      It is strongly recommended that you create a new branch from the locally exported version of the server project. This will ensure that changes made in Teamwork Cloud can be merged with local changes by using a correct common ancestor.

      If the Question dialog appears, click Yes to automatically create a new branch from the locally exported version. It will automatically create new branches for the project and each of its used projects if they need an update.

      If you click No, the branch that is opened or selected in the Manage Projects dialog is specified automatically.

  3. Click Update when you are done. An updated version of the project with the contents of the local project is created in the selected branch.

The server project will not be updated if the tool recognizes that the local project is the same version as the server project. The same rule applies to used projects. 


Used projects

If the .szip version of the project contains used projects, their status can be reviewed in the Update from Local Project dialog when the project updates. To review updates, click More in the bottom-left corner of the dialog. 

Depending on the changes made in the used project, the following actions can be chosen automatically when the project updates: 

  • Keep Version #<number>: if the used project version is the same as the one on the server (for example, it has not been modified locally), the same version of that used project is kept when the main project updates. 
  • Use Version #<number>: if the used project version on the server differs from the one in the local file, the version that is both available on the server and matches the local file contents is used.
  • Add to server: if a new used project is added to the local file and it does not yet exist in the server project, it is added to the server upon the main project update.

  • Update: if the local file contains used project-related changes, the changes are applied to the server project upon the main project update.

During a server project update from a local project, commits to branches being updated are not allowed, meaning other users working on the same project branch cannot commit the changes they have made.