Need for "not" logic when matching substrings in reporter
Bug #1618993 reported by
Chris Sharp
This bug affects 6 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Currently, the reporter offers "Contains Matching substring" and "Contains Matching substring (ignore case)" options for filter operators, and I have hit a situation where I need to reverse that logic. Unfortunately, there's not currently an option to do so, so I plan to add that feature.
| Changed in evergreen: | |
| importance: | Undecided → Wishlist |
| assignee: | nobody → Chris Sharp (chrissharp123) |
| Changed in evergreen: | |
| assignee: | Chris Sharp (chrissharp123) → nobody |
| tags: | added: reports |
Revision history for this message
| Terran McCanna (tmccanna) wrote | #1 |
| Changed in evergreen: | |
| status: | New → Confirmed |
To post a comment you must log in.
I just ran into another situation today where I could have really used a "does not equal" or "does not contain" string operator.