Hi Andy,

I use custom menus as well and faced the same issue after our totara was updated from 2.6.17(I think)  to 2.7.3 the fields were working fine but for some reason all the audiences that were set to contains "some menu item" were changed to does not contain "some menu item".

I deducted that there was something wrong with the way it was displaying and the underlying code was (hopefully) not bad. what I did is not mess with the rules that were working properly before the upgrade but displaying the wrong text (does not contain vs. contains) and any new rules I used that I wanted to show that the menu item was a certain value I used does not contain. this works perfectly.

Hopefully it is only a language problem or something easy like that because I dread going through and fixing the 100+ rules I have set up or worse data loss.

Peter