We recently fixed unexpected API behavior that returned all users after running a teams query with an empty array for the ids argument. Now, if you send an empty array, it will return no users.
query {
teams (ids:[]) {
id
}
}We recently fixed unexpected API behavior that returned all users after running a teams query with an empty array for the ids argument. Now, if you send an empty array, it will return no users.
query {
teams (ids:[]) {
id
}
}Starting April 15th, 2023, we will deprecate connections from Windows Server 2012 R2, Windows 8.1, or earlier because they use weak ciphers. This update will not impact support for TLS 1.3.
Check out this document to find out which systems this update impacts, how to know if you are affected, and which ciphers you can use!
Please take note of the following updates to the boards object:
add_teams_to_board mutation allows you to add teams to a board.add_subscribers_to_board mutation. Please use the add_users_to_workspace or add_users_to_board mutations instead.We recently added the country_code field to the account object. It will return the two-letter country code where the first account admin is located. Check out our documentation to learn more!
We added a new field and argument to the users object to expand its functionality:
last_activity field returns the last date and time the user was active.name argument allows you to conduct a fuzzy search of users by name.Check out all of the details about these updates in our documentation!
Due to popular demand, we recently released a new mutation that allows you to update a group! You can view this mutation's details, including the code samples, arguments, and accepted attribute values, in our documentation. Happy updating!
mutation {
update_group (board_id: 12345678, group_id: "today", group_attribute: color, new_value: "red") {
id
}
}As a reminder, we will turn phone column validations back on starting December 1st, 2022!
Please ensure that your phone numbers follow the appropriate format to avoid errors and losing data. You can find examples to help you structure your numbers correctly in the phone column doc.
We recently made bug fixes that impact the items_by_column_values object:
created_at field will appear in reverse chronological order, with the most recent dates first.You can now update the people column with an email address by sending a string with the column's new value. Check out the code sample below!
mutation {
change_simple_column_value(item_id: 123456789, board_id: 987654321, column_id: "person", value: "[email protected]") {
id
}
}We've added four new fields to the workspaces object:
settings returns the workspaces settingsowners_subscribers returns the workspaces owner'steam_subscribers returns the teams subscribed to the workspaceusers_subscribers returns the users subscribed to the workspaceCheck out our workspaces doc to find out more!