Known issues with Teamwork.com API

Background context: Previously if a user didn't have their working hours set, we would return fake 8h Monday to Friday. The idea was that when the user clicked on 'Save' this would also save those 8h in the database.

There were cases where a users profile was never updated and this was causing inconsistencies with other parts of Teamwork.com as the working hours appeared as 0 hours per day.

Recent rollout: We have made a change in a code rollout that will make sure that hours will be added to the DB as soon as a profile is saved.

What should I do: If you notice that working hours is not being returned for selected users. Take note of their user id > follow the steps to edit a users details and save. You don't need to alter anything for the working hours to be added to the DB.

Background context: If you use the Add project custom field value endpoint to add a new custom field value. This will create a new value as specified and this value will gets its own unique id.

If you use the same endpoint to add a new value, this will gets its own id as well.

Known issue: If you make a request to delete a custom field value with the Delete an existing project custom field value endpoint, this will delete the value linked to the id that you specified. This is working as expected.

However, if you have used the Add project custom field value endpoint multiple times for the same custom field, the previous custom field value will appear.

What should I do: - There are two options

  1. Once you make your initial request to add a custom field value, take note of the unique value id that gets returned in the response payload. Use this id along with the site level custom field id to make a request with the update an existing project custom field value endpoint

  2. You can use the update project endpoint and pass in the custom field values with the site level custom field ids only. Please note that this option requires you to pass in all of the custom field information for the project. Omitting a custom field with this payload will result in the custom field being removed from the project.

Code samples for the requests mentioned above

POST: Add project custom field value.js

PUT: Add or update custom field(s) values on a project.js

PATCH: Update an existing project custom field value.js