User
model currently has a CapacityPerWeek
property, which we're removing soon. This property is getting it's own endpoint: /users/{userId}/capacity
GET
and PUT
methods to retrieve and edit the user's weekly capacity. The GET
model looks like this:IsBillableByDefault
,which decides whether time entries created on that project are marked as billable or not. This is either set by the project template, or if no project template was used for creation, by whether the project has a company or not. In the case of a company, the times are marked as billed, otherwise the times are marked as not billable.IsBillableByDefault
property on the project template from a boolean
to a string
field with the possible values: on, off, auto
.auto
option is set, the IsBillableByDefault
of the project on project creation will be set according to the company rule, so true
if a company is set and false
if no company is set.allow-multi-user-assignment
.assign-user-to-task
, there is now an additional ActionValue
removeOldAssignments
. In order to assign multiple users to a task, you need the set this value to false
. You can also add multiple assign-user-to-task
actions to an automation in order to assign multiple users for a single trigger.task-create-project
and task-create-private
, the task
ActionValue
now has an array assigneeIds
instead of a single assigneeId
. However, you cannot assign multiple users to private tasks.