Currently the comparisons "equal to" and "contains" operate the same in branching rules when applied to multi-select lists. I would like for them to operate per their true meanings. To illustrate -

I have a multi-select list, Geographic Area Served, with the following options:
Houston area
Austin area
Southwestern Colorado
State of Texas
Other

We will use two cases in this example
1. The user selects only “Other”
2. The user selects “Houston area” and “Other”

When I run a report in GLM showing the two different cases’ values, it displays as
Case 1. “Other”
Case 2. “Houston area; Other”

I want a question group to display if the only option the user selects is “Other”. If they select any other combination of options, with or without “Other”, then don’t display the group. So for the example cases, display the group in Case 1, but not in Case 2. To me, it is intuitively obvious that this would translate to a branching rule as
Geographic Area Served Equal To Other

Puzzlingly, that is not how it operates in GLM. As it works now, if the user selects Other at all, the group will display. So it is acting as if I have set a rule as
Geographic Area Contains Other

My only work around is rather than have a single rule (Geographic Area Served Equal To Other), I must create a rule group with five rules
Geographic Area Served Equal To Other
Geographic Area Served Not Equal To Houston area
Geographic Area Served Not Equal To Austin area
Geographic Area Served Not Equal To Southwestern Colorado
Geographic Area Served Not Equal To State of Texas

I would like for Equal To to actually mean “equal to” in branching logic applied to multiselect lists.