Make "support wildcards" functionality visible and understandable to report users

The new feature introduced in 7.1: Querying on string properties

https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.1.0?topic=builder-querying-string-properties

"A Supports wildcards checkbox is added for query conditions on string properties. By default, the checkbox is selected when the "contains" or "does not contain" operator is selected and cleared for all the other operators. However, you can change support for wildcards based on your requirements. If you select the Supports wildcards check box is selected, an unquoted asterisk is interpreted as a wildcard for all the operators. If the Supports wildcards checkbox is cleared, an unquoted asterisk is interpreted literally."

is a very nice enhancement as you are now able to use wildcards also in "is" conditions.

in general: very helpful and while editing the report clear to understand as the new checkbox is there and the tooltip helps to understand it

in case of creating reports for reuse purpose, users are lost:

• when running the report, the filter does not show any information about "support wildcard yes/no", but always shows the information "Enter text or use wildcards: * for any characters, or "" for phrases."
• the "My Choices" overview only shows the condition without any further information

Unfortunately I see the current behavior as a usability issue:

1) independent of which condition you choose, the default setting is "support wildcard"

2) the filter behaves quite differently  dependent of using "support wildcard" or not (not only in case of ID, there it might be a bit easier / more obvious, that an ID can not contain "*", but also e.g. with title) - some examples

• title "contains" incl. support wildcard -> * shows all, "*" filters on * in title -> fits to info
• title "contains" without support wildcard -> * and "*" filters only in title, no wildcard support -> info wrong
• title "is" incl. support wildcard -> * shows all -> no info at all, user does not know if wildcard works or not
• title "is" without support wildcard -> * does not work (unless a title really is *) -> no info at all, user does not know that * does not work as wildcard

3) if you select "support wildcard" the information shown in the filter section is correct, but if you don't select "support wildcard", it is again not correct

From my point of view, this is another example where you introduced a useful new feature, but did not finalize it. Please add a hint for the user that fits depending on the selection in the condition

• into the filter section (similar to today's info, but fitting to the real behavior)
• into the "my choice" view (e.g. by showing if "support wildcard" is selected or not)

Hope, that you can understand and follow my concern. Unfortunately, these are the (smaller) things, why people do not like the tool...