Bug 1288848 - allow advanced options in rules engine
Summary: allow advanced options in rules engine
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Internal Tools
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-06 13:55 UTC by Yaniv Lavi
Modified: 2018-01-23 03:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-21 11:12:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Yaniv Lavi 2015-12-06 13:55:43 UTC
Description of problem:
In Bugzilla search you are able to filter with advanced options like contains\regex and so on. Some field allow this currently and some do not like target milestone. To make rules simple this is needed. Please add a advanced option for all fields.

Comment 1 Jeff Fearn 🐞 2015-12-07 02:41:53 UTC
I tested Custom Search on BZ 5.0 searching on Target Milestone for 
.*4.2.*, found bugs with TM like 0.14.2, 3.4.2 and 4.2.

Comment 2 Yaniv Lavi 2015-12-07 11:17:23 UTC
This RFE is on rules engine, not the search. 
Search has had this for many versions, this is to allow same use in rules engine.

Comment 3 Jeff Fearn 🐞 2016-08-16 02:20:07 UTC
Hi Yaniv, when you add a new criterion one of the opt-groups is "Custom field" which seems to have every field listed and gives you the option to do a regex match. Is there a specific list of fields you need that isn't available in that part of the drop down?

Comment 4 Yaniv Lavi 2016-08-21 11:12:32 UTC
(In reply to Jeff Fearn from comment #3)
> Hi Yaniv, when you add a new criterion one of the opt-groups is "Custom
> field" which seems to have every field listed and gives you the option to do
> a regex match. Is there a specific list of fields you need that isn't
> available in that part of the drop down?

I didn't notice this. Thanks! I'll use that.


Note You need to log in before you can comment on or make changes to this bug.