Modify ↓
Opened 20 years ago
Closed 20 years ago
#1063 closed enhancement (fixed)
change custom query with custom ticket text fields from exact match to contain
| Reported by: | Owned by: | Christopher Lenz | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.9 |
| Component: | ticket system | Version: | 0.8 |
| Severity: | normal | Keywords: | query |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
It would be wonderful if the for custom ticket text fields the custom query could be changed from an exact match to a contain match like the keyword field.
Another solution would be to add a "match type" combo to each text field, where one could specify the match operation
Attachments (0)
Change History (2)
comment:1 by , 20 years ago
| Component: | report system → ticket system |
|---|---|
| Keywords: | query added |
| Milestone: | → 0.9 |
| Owner: | changed from to |
| Status: | new → assigned |
comment:2 by , 20 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
New query branch has been merged into trunk in [1162]. The new interface has various match modes for text fields, such as "contains", "doesn't contain", "starts with", "ends with", etc.
Note:
See TracTickets
for help on using tickets.
The new query branch provides this capability.