When adding a multi-select field as a trigger in Rules, the only options for selections are “contains any” or “contains all”. Please consider adding “contains only” so we can create multiple rules based on exact selections.
11 Likes
Hello @Christina_Davies, happy to help here.
I just want to understand your question. Doesn’t “contains any” work the same as if it would be to “contains only”. This way you can select one of the values you have in that field.
For example:
What I’m saying is that if field “Test field” is changed and contains just the value “Option 1” will trigger the following actions: Add subtasks and add a comment “Hello”.
Does this makes sense? Please let me know if I didn’t get your question correctly.
Cheers,
4 Likes
Hi @chilosada,
Thank you for your reply! Perhaps a scenario would help:
I need a series of rules which would add subtasks based on the selections in the multi-select field. I’ll use the Test Field example you gave.
Rule 1: a user selects only Option 1; subtask A and B are added
Rule 2: a user selects Option 1, Option 2 and Option 3; subtasks C, D, E, F and G are added
If I use “contains any,” and a user selects Options 1, 2, and 3, that will trigger Rule 2. However, Rule 1 will also run every time, so I would get subtasks A-G added when it should only be C-G. If Rule 1 was set to “Contains only”, it would not run when Options 2 and 3 were also selected.
5 Likes
Hello @Christina_Davies thanks for your clarification.
I just did a test and I now understand what you were saying.
Hopefully @Emily_Roman can help us sharing this idea with the product team.
Please let me know if there is anything I can do for you.
4 Likes
I have not built a rule with such scenario but I understand how that would come in very handy. I added my vote +1
4 Likes
Thanks all, I’ve just filed a task to share the idea with our team, hopefully this is something we can consider in the future!
5 Likes
@Marie @Emily_Roman has there been any progress towards this rule? I am running into the same issue. Thank you.
3 Likes
We don’t have many rules on our multi-select fields but have started implementing rules on those recently, and are running into the same issue.
This negates the whole purpose of multi-select. The work-around would be to have a different field altogether but then our fields list is already quite stealthy as is. And considering when a task is multi-homed on various projects and every field from every project a task is attached also inherits those fields, it has become quite cumbersome for our people working said tasks. It’s me, I am our people working said tasks! 
This is my first encounter with upvoting so I hope I do this right…
Upvoted!
3 Likes
Hi guys,
I have the same need. I’ve been struggling with the multiple select custom fields conditions because we only have “Contains All or Any” options. Will be great to have “Is” or “Contain Only”. Not having this conditional options made me move from Multiple Select custom field to Single Select and combine the options my self. Below I share an example why this fails when the rules evaluate the fields content.
Multiple Select Custom Field Options:
- Option A
- Option B
- Option C
Rule 1
When Multiple Select Custom Field Contains All
- Option A
Add Sub Task 1
Rule 2
When Multiple Select Custom Field Contains All
- Option A and Option B
Add Sub Task 2
Both rules executes when the custom field has Option A but here is the difference between what we need.
Rule 1
When Multiple Select Custom Field Contains All
- Option A
Add Sub Task 1
Rule 2
When Multiple Select Custom Field IS or CONTAINS ONLY
- Option A and Option B
Add Sub Task 2
Only the on of the rules will run when only when the selected options are the same evaluated in every condition. Rule 2 will will only run when both options are selected. And Rule 1 will not run unless I only select Option A.
Hope I make my self clear and that we can have this available.
Best regards,
JRM
4 Likes
I agree. The Multi-Select is a wonderful tool. Any time you make changes to the multi-select. Rules trigger and it is not exactly the scenario I was looking for. If you do not watch out your rules can put in the wrong data.
Really limiting.
2 Likes
I have also now run into a situation where I need this option for workflow rules. Any update on this from the Asana product team would be appreciated.
Any update on this topic? I have also run into a similar situation in rules.
@Rey_A_Llenes1 and @Shalley_Asthana,
Asana does not comment on unreleased features, so there won’t be any information updates available unless/until they release something, sorry.
FYI we just released this “only” capability for multi-select and people custom fields in our Flowsana integration’s rules.
Thanks for letting me know! Appreciate your response.
Any update on this rule? A Contains Only option would definitely help.
Running into this problem myself with the new rule builder.
- When Task is moved to a section
- Check if section is “Accepted” and Channel contains any of Email
- Do this “add collaborators” and “create subtasks”
I have branches in this rule to check for Channel Doximity and Channel Paid Media - however if someone selects multiple channels, they do not get all subtasks - only those for the first successful trigger.
I have also tried to change this “Check If” to “contains all of” vs “contains any of” and the SAVE button does not turn blue to accept this change. Does this verbiage actually mean anything different to the platform?
Having a “Contains only” option would be a great improvement for situations where you must declare something as an absolute reference. This is extremely necessary; the current options are too confusing (it would also help to count on a small explanatory note or summary that could appear on that big empty column space that lacks function when you’re setting up the conditionals while within that menu, telling about what each of them does and their application)!
2 Likes
I’ve been running into this constantly and it’s quite frustrating. I have a broad set of rules that allow users to select options from custom fields, and the rules then populate tasks with subtasks based on the options selected. Without a “contains only” option in the rules, they trigger each other multiple times.
For example, one of the rules checks which options are set for a “Website Assets” field. If someone selects “Blog” and “Hero Banner,” Asana creates the associated subtasks for those items twice and I have to manually delete the duplicates. This is counterproductive and makes for a clunky user experience.
Help with this please - just trying to bring this back up to the top. This would make the multi select field so valuable!
6 Likes
How has this not been fixed yet Asana? This is a pretty common rule need
4 Likes