Bug 141005 - no way to filter on "alias" when querying
no way to filter on "alias" when querying
Status: CLOSED NOTABUG
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
2.17
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: David Lawrence
Mike MacKenzie
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-27 17:21 EST by Todd Warner
Modified: 2007-04-18 13:15 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-27 17:45:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Todd Warner 2004-11-27 17:21:30 EST
SSIA

I want to filter a query based on the alias (for example) rhn360sat. I can't see
a way to do it.
Comment 1 David Lawrence 2004-11-27 17:45:10 EST
Should be able to do this using the boolean advanced section near the bottom of the query 
page. For example:

https://bugzilla.redhat.com/bugzilla/buglist.cgi?
query_format=&short_desc_type=allwordssubstr&short_desc=&component_text=&long_d
esc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&st
atus_whiteboard_type=allwordssubstr&status_whiteboard=&fixed_in_type=allwordssubstr
&fixed_in=&qa_whiteboard_type=allwordssubstr&qa_whiteboard=&devel_whiteboard_type
=allwordssubstr&devel_whiteboard=&keywords_type=allwords&keywords=&cust_facing=
&cust_facing_type=substring&emailassigned_to1=1&emailtype1=exact&email1=&emailas
signed_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=exact&e
mail2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldv
alue=&cmdtype=doit&remaction=run&namedcmd=allmypackages&order=Bug+Number+
Ascending&field0-0-0=alias&type0-0-0=equals&value0-0-0=rhn360sat

Also if you know the exact alias, then you can just type it into the Goto bug # field at the 
top of each page and it will load the bug for you.


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