[Status: Launched 🚀] Custom Fields should have a real checkbox

@Anup thanks for submitting this product request!

No problem.  IS something going to be done? 

@Anhup I don't believe this is currently being worked on, but I'm double checking to confirm.

@Stephanie any idea when this feature will be available in Wrike updates?

Hi Mitja, filling in for Stephanie here :) I don't have a timeframe to share at this moment, but we'll make sure to update the thread if we have any news. Thank you for keeping this thread active!

Hi,

Same here. This is one of the last features I really need for my company. I just need to assign a list of suppliers to a task.

keep me in touch.

Thx

This feature is strongly desired by our company.  For example, we work with external scientific experts, with expertise across a broad spectrum of categories.  We would like to represent the typically 3-6 categories of expertise for each person.  We can do this a very large folder hierarchy, but that is cumbersome.  We would like to be able to do this instead with a Custom Field in which multiple items can be tagged, and then searched upon.

My team also strongly desires this feature. We have large, complex projects for our customer onboarding process and a subset of those are assigned to a specific end user. There is no way for us to filter / report on all tasks that are assigned for a given user. For now we have settled on a CF checkbox for indicating if a task is user-specific, but the more ideal solution would be to be able to select exactly which users the task applies to.

Thanks for the input here Laura. The Product Team is aware of the suggestion here and if I have any new information I'll update you here.

I'm wondering if your Folder structure could help with this for now? For example, you could have a Folder named 'Clients' and create a Subfolder for each client with their jobs or tasks created/tagged there. This way when running a Report you can source it from the specific client Folder.

If something like this interests you let me know, I'll be happy to discuss 👍

This would be extremely helpful for our team. We're currently having to employ elaborate workarounds (especially with folder structure) that make this tool inefficient and cumbersome. Thanks for your efforts to improve the tool!

Definitely want this feature. Super important.

Please introduce this feature. This would really improve how we could use Wrike for our organization.

That would be really useful for our company. I hope that Wrike take it in consideration!

We would love this too! I'm in Communication for a university, and many of our projects touch multiple audiences (e.g.: first-time freshmen, transfer students, parents, etc). Having this feature would make it easier to track the comm flows for all of our different populations. Please implement!

Hey Wrike team, this request came one year and a half ago - any plans to add it to your roadmap or not?

This is really important!!!

We are looking for the EXACT same thing and need it soon!!!!

OH - I needed this feature yesterday. PLEASE add to roadmap soon.

In addition to voicing support for this feature please see Wrike APIv4 documentation for all three custom field endpoints (create, query, and modify). The documentation includes "Multiple" as one of the available values for the "type" parameter. It is listed in both the request and response parameters table (save the query endpoint).

In addition, inside the settings object is a values array, and per current documentation this applies to dropdown and multi-select types.

The option for multiple is also not available within the application itself.

When I create a new custom field with data type of Multiple, the API returns the field as a Multiple type but the application lists it as Text.

curl -X POST \
'https://www.wrike.com/api/v4/customfields?title=Test%20Multiselect&type=Multiple' \
-H 'Authorization: Bearer <token>' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d settings=%7B%22values%22%3A%5B%22a%22%2C%22b%22%2C%22c%22%5D%7D

json response:

{
   "kind": "customfields",
   "data": [
      {
         "id": "<id>",
         "accountId": "<accountId>",
         "title": "Test Multiselect",
         "type": "Multiple",
         "sharedIds": [],
         "settings": {
            "inheritanceType": "All",
            "values": [
               "a",
               "b",
               "c"
            ]
         }
      }
   ]
}

Lastly, when accessing the custom field via the application the option to edit the field is not present, whereas it is present for dropdown custom fields.

I am sure there is a rationale but with the provided documentation, product request above, and behaviors I've just logged here, the situation is confusing in my opinion. If possible, could you address some of these, what I consider, inconsistencies?

Update: It appears that multiple select is supported as a type of custom field which suggests that between now and March Wrike added the feature.

@Bryan Thank you for all of the screenshots there! I've created a Support Ticket related to your comment so that the team can look into the documentation. Multiselect checkboxes in tasks aren't available yet, but the team is working on them and they should be available soon 🙌

A couple improvements are needed to the multiple select field:

- When an existing dropdown value is changed in the Edit Custom Field window, it should change all instances of that value within the tasks.

- I should be able to add a dropdown value within the task itself.  It's a pain to have to exit the task, add the dropdown value in Edit Custom Field and then go back into the task to add it.

** Look to Airtable for an example of how to do this well.

Hello! I agree with Gahl Shalev on the 2 enhancements mentioned. I have one more:

- Request forms should now support multiple select and be able to be mapped to a Multiple Select custom field. Right now, there is no multiselect questions for the request form and your Multiple Select custom field can't be mapped at all.

Thanks!

@Gahl, thanks for your feedback here. I've passed this onto the team. This request is a little different to what was originally asked. It would be great if you could create a new thread where people can vote and the Product Team can refer to.

You can share the link to the new feedback post here so @Faris and others can vote for it 👍