Prior to moving to v.14, we were finding that a list could be built and saved. When the criteria is reviewed there was a "new" criteria added by Tessitura that the user did not request. For instance a list with just and ID # is created but when the user looks at it there is a criteria of Season (Order) IN Music 2014-15, Music 2015-16. Something the user NEVER would be looking for and is not in their own lists.
We were told this would go away in v.14 -- it has not. Just wanted to alert folks -- another ticket is being opened
Weird. To be sure, we've never seen this issue at our organization: v12.5, v14 or v14.1. Do you have any automated processes that update lists or list criteria? The other question would be whether you have other users building lists who might be adding that criteria to their lists?
I do have an issue that cropped up after the v14.1 upgrade with one of my custom criteria, actually a custom plan element, which is that you can select and configure it as a criteria, but it never populates into the actual query being run. We have an open ticket on the issue. Other custom criteria that I've tested have all worked normally.