Keyword	Format	Example
build (not supported for views)	build:<build_name or build_number> Note: You can only search by one build at a time. Other acceptable syntax: build:'123' - searches for build which contains substring '123' build:+123 - searches for build with name 123 build:+'123string' - searches for build with name equal to '123string' Tip: You can use the build:any keyword, along with specifying state:Fixed to find issues fixed in a previous build. For example, to find a 'FNH.MUST' issue fixed in a previous build, search for `build:any state:Fixed FNH.MUST`.	build:build_2 or build:beta
bugId	bugId:<ID_number> Note: To use this keyword, you must integrate Static Code Analysis with your bug tracker. For more information, see Integrating bug tracking with Static Code Analysis.	bugId:15
category	category:<issue_category>,<issue_category>...	category:"buffer overflow"
cited	cited:'<time1>'-'<time2>' Note: Acceptable time formats are 'yyyy-mm-dd hh:mm:ss' or 'yyyy-mm-dd'. Other acceptable syntax: cited:<date> - searches for status changes for the day you specify cited:'<date>'-'now' - searches for status changes from the date you specify right up to the current date cited:today - searches for all status changes made in the last 24 hours cited:week - searches for all the status changes made in the last 7 days Both the cited and citedby keywords are applicable only to issues. You must enable grouping:off to use them.	cited:'2011-10-24 07:45:30'-'2011-11-24 21:30:00' cited:2011-11-24 cited:'2011-11-24'-'now' cited:today cited:week
citedby	citedby:<user_name>	citedby:jsmith
code	code:<issue_code>,<issue_code>...	code:NPD.GEN.MUST, npd.const.call
comment	comment:<"issue comment"> Note: Use quotes for expressions that contain spaces or punctuation.	comment:"check with bob on this issue"
diff (not supported for views)	diff<build_1>,<build_2>	diff:build_abc,build_def
entity	entity:<entity_name>,<entity_name>...	entity:get_file_type
file	file:<filename>,<filename>...	file:htmlparser
grouping (not supported for views)	grouping:<'on' or 'off'>	grouping:off
id	id:<ID_number>,<ID_number>...	id:33,59,149-160
line	line:<line_number>,<line_number>...	line:1-50,233
message	message:<message_string>	message:my_var
module	module:<module_name>	module:my_module
owner	owner:<name or group> Note: Searches user accounts, group accounts and the `.sow` file.	owner:smith,lee,devteam
recommended	recommended:<'on' or 'off'> recommended:<'true' or 'false'> Note: The 'recommended' keyword is used to filter by SmartRank issues. 'On/True' returns SmartRank issues. 'Off/False" shows issues not meeting the SmartRank threshold. Omitting this keyword returns both. For more information, see Using SmartRank to prioritize issues.	recommended:on
reference	reference:<ref_string>,<ref_string>	reference:20,cast.ptr
severity	severity:<severity_name or severity_number>	severity:critical,4,error, 2-4
state (not supported for views)	state:<state_name>,<"state name">...	state:existing,fixed
status	status:<status_name>,<"statusname">	status:ignore,"fix in next release"
taxonomy	taxonomy:<taxonomy_name>,<"taxonomy name">	taxonomy:"MISRA C","MISRA C++"