2017-05-02 Release: Wrike Task ID and Dropdown Support

In this release, we have lots of different small bugfixes, but two new major features for Wrike: Task ID and Dropdown support. Read more about them below!

New Feature: Wrike Task ID Support

This is a simple change, but a good one: Now, Wrike "Task Number" is available to map to the Description footer or a custom field in any other tool. Simple, to the point, and effective!

New Feature: Wrike Dropdown Support for Custom Fields

Until now, it was impossible to explicitly map values with a Wrike DropDown custom field. Wrike has now added their DropDown values to their API, which opens the possibility to map them with another listable field.

Even though it wasn't fully supported in the past, you could have still mapped Dropdown fields. They used to act as simple 1:1 transfers, and many of the DropDown features weren't supported. If you have this set up in one of your syncs already, the system will continue to sync as it did before, but it will now reject any value that's not part of the DropDown values. If the other side's field is set to a value that's not part of the predefined ones on the Wrike side, the Wrike DropDown custom field will be cleared.

If you want to define the mapping, you'll have to edit your sync, remove the association with the DropDown custom field, and finally add it back. You will see a cog on the associations that will let you define the mapping more deeply. Going forward, any new association between a listable field and a Wrike DropDown custom field will show a cog, so that you can now specify what goes where.