Bug 1618664

Summary:	Custom Search '(' toggle is not working
Product:	[Community] Bugzilla	Reporter:	Jose Luis Franco <jfrancoa>
Component:	Query/Bug List	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	bkearney, ebenes, fweimer, jfearn, jsuchane, khong, lsvaty, mleitner, qgong, sbonazzo, vashirov, xiawu
Target Milestone:	5.0-RH2
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.0.4.rh13	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-13 02:13:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jose Luis Franco 2018-08-17 09:15:59 UTC

Description of problem:

When doing a custom bugzilla search, the parenthesis toggle is not working as expected. In previous versions, when pressing that button a new subset of options were displayed in which you could choose if it needed to match all of the condition or any. But now, when clicking on it nothing is being made.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Access https://bugzilla5.redhat.com
2. Go to Search -> Advanced Search
3. Open the Custom Search section, choose "Show Advanced Features"
4. Click in the '(' button.

Actual results:
Nothing is being made.

Expected results:
A new subset of conditions is displayed in which you can choose the behavior to match all or any of the conditions.

Additional info:

Comment 1 Rony Gong 🔥 2018-08-24 05:07:26 UTC

Tested on QA environment
Result: Pass

Comment 2 Jeff Fearn 🐞 2018-12-14 08:32:42 UTC

*** Bug 1658261 has been marked as a duplicate of this bug. ***

Comment 3 Jeff Fearn 🐞 2018-12-14 08:32:51 UTC

*** Bug 1659339 has been marked as a duplicate of this bug. ***

Comment 4 Jeff Fearn 🐞 2018-12-14 09:06:50 UTC

*** Bug 1659079 has been marked as a duplicate of this bug. ***

Comment 5 Jeff Fearn 🐞 2018-12-18 11:44:07 UTC

*** Bug 1660463 has been marked as a duplicate of this bug. ***

Comment 7 Jeff Fearn 🐞 2019-01-13 23:35:17 UTC

*** Bug 1663525 has been marked as a duplicate of this bug. ***

Comment 8 Jeff Fearn 🐞 2019-01-17 21:48:36 UTC

*** Bug 1667137 has been marked as a duplicate of this bug. ***

Comment 10 Jeff Fearn 🐞 2019-02-06 07:11:06 UTC

This change has been deployed to partner Bugzilla [1] for pre-release testing, if your testing reveals any issues please update this bug.

1: https://partner-bugzilla.redhat.com/

Comment 11 Jeff Fearn 🐞 2019-02-07 00:08:29 UTC

*** Bug 1673115 has been marked as a duplicate of this bug. ***

Comment 12 Marcelo Ricardo Leitner 2019-02-07 00:49:49 UTC

(In reply to Jeff Fearn from comment #10)
> This change has been deployed to partner Bugzilla [1] for pre-release
> testing, if your testing reveals any issues please update this bug.
> 
> 1: https://partner-bugzilla.redhat.com/

Quick testing, worked for me.


On a side note, how frequent is the data snapshot updated?
Asking because I noticed this bug:
https://partner-bugzilla.redhat.com/show_bug.cgi?id=1618538
is still public in there, while I have marked it as private:
https://bugzilla.redhat.com/show_bug.cgi?id=1618538
though it seems I did so after the data snapshot.

Comment 13 Jeff Fearn 🐞 2019-02-07 00:56:24 UTC

(In reply to Marcelo Ricardo Leitner from comment #12)
> On a side note, how frequent is the data snapshot updated?
> Asking because I noticed this bug:
> https://partner-bugzilla.redhat.com/show_bug.cgi?id=1618538
> is still public in there, while I have marked it as private:
> https://bugzilla.redhat.com/show_bug.cgi?id=1618538
> though it seems I did so after the data snapshot.

There is no schedule for updating partner, it is done on request, provided there is sufficient business reasons to justify the process.

Comment 14 Jeff Fearn 🐞 2019-02-13 02:13:11 UTC

This change is now live. If there are any issues, do not reopen this bug.                                                                                                           
Instead, you should create a new bug and reference this bug.