Search for issues with a combination of filters and display the search results.<\/p>\n
evsearch [-n] [-i] [-c field1,field2, … fieldn] [-f myfile.txt] [-s skipcount] [-l pagelength] [-p reportID] [-T templatefile] [field1=value1[;value2[;valuen]]] [field2=value1[;value2[;valuen]]] … … [q]<\/p>\n
evsearch -r [-n] [-s skipcount] [-l pagelength]<\/p>\n
[field1=value1[;value2[;valuen]] [field2=value1[;value2[;valuen]]] … ….[q]<\/p>\n
evsearch -d<\/p>\n
This command allows the user to search for issues that meet specified filter criteria, and displays results (field values) for issues that match the filter criteria. The user must provide both search criteria, and a list of fields to display. Note that any field selected must be on the detailed report layout for the business area and project currently selected, and that the user must have permission to read the fields.<\/p>\n
The user may specify search criteria in two ways, either on the command line, or through an interactive menu.<\/p>\n
On the command line, the user may specify fields and fields values to use as search criteria. If the command line is terminated by the letter q, the search will be immediately executed. If the command line does not terminate with the letter q, any search criteria specified on the command line will be passed along to the interactive menu, for additional filter criteria specification.<\/p>\n
By default, command-line-specified fields must be identified by their Display Titles. For fields with a display type of List, values must be identified by their display titles. When the -i<\/span> option is used, fields must be identified by their fixed database names, and list values must be identified by their fixed names (for non-UDF lists), or by their internal list ID\u2019s (for UDF lists). The evmeta<\/span> command displays both of these list names for all list items.<\/p>\n A search may be performed for more than one value of a field by using a semi-colon to separate the values. For example:<\/p>\n STATUS=OPEN;FIXED;CLOSED<\/span><\/p>\n will search for issues with a status of Open, Fixed or Closed.<\/p>\n A variety of formats are supported for searching date fields:<\/p>\n These formats may be used either on the CLI, or through the interactive menu.<\/p>\n Keyword searching is also supported through the CLI. On the command line, use the -k<\/span> option, and provide one or more keywords as a space-delimited list. When performing a keyword search, all text fields in the issue are searched for occurrences of the keywords entered. When multiple keywords are entered, the search will return issues that match any of the keywords. For example:<\/p>\n evsearch -k \u2018core stack\u2019 q<\/span><\/p>\n will search for issues containing either the word \u2018core\u2019 or the word \u2018stack\u2019. Keyword search criteria must be specified on the command line. This option is not available through the interactive menu.<\/p>\n If a command line is not terminated with the letter q<\/span>, evsearch<\/span> will display a menu of all the fields available as search criteria, with each field identified by a number. After the menu is displayed, the user will see the prompt:<\/p>\n Enter number or q to submit:<\/span>.<\/p>\n When a field number is entered, evsearch will prompt for the search value. If the field is a list, the list of available values for that list will be displayed.<\/p>\n After all desired search criteria have been entered, press q<\/span> to exit the menu and submit the search query to ExtraView.<\/p>\n There are three ways of specifying the list of fields to be displayed:<\/p>\n By default, only fields on the Detailed Report<\/b> layout of the user’s current Business Area and Project, to which the user has read permission, may be requested. You cannot request fields that do not appear on the detailed report for the currently selected business area, project and user role. However, the -p<\/span> option may be used to specify a different report to be used as the source of field data.<\/p>\n Note: Even though attachments may be displayed on a report layout, evsearch<\/span> cannot display attachments. To view attachments, users may use the evfiles<\/span> command.<\/p>\n If the file $HOME\/.evsearch<\/span> exists, and neither the -c<\/span> option nor the -f<\/span> option are provided, evsearch<\/span> will use the contents of this file as the list of field names whose values will be displayed. The format of this file is:<\/p>\n evsearch -i status=NEW q<\/span> The output from a search can be piped to the evxmlc command, to give control over the formatting of the output.<\/p>\n Search for issues with a combination of filters and display the search results. SYNOPSIS evsearch [-n] [-i] [-c field1,field2, … fieldn] [-f myfile.txt] [-s skipcount] [-l pagelength] [-p reportID] [-T templatefile] [field1=value1[;value2[;valuen]]] [field2=value1[;value2[;valuen]]] … … [q] evsearch -r [-n] [-s skipcount] [-l pagelength] [field1=value1[;value2[;valuen]] [field2=value1[;value2[;valuen]]] … ….[q] evsearch -d DESCRIPTION This command allows the user…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":24277,"menu_order":60,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_lmt_disableupdate":"no","_lmt_disable":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"class_list":["post-24309","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\n\n\n
\n datefield=6\/24\/2003<\/td>\n Searches for a date equal to 6\/24\/2003<\/td>\n<\/tr>\n \n datefield=\u22126\/24\/2003<\/td>\n Searches for dates up to and including 6\/24\/2003<\/td>\n<\/tr>\n \n datefield=6\/24\/2003-6\/30\/2003<\/td>\n Searches for all dates between 6\/24\/2003 and 6\/30\/2003 inclusive<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n List of Fields to Display<\/h4>\n
\n
\n
OPTIONS<\/h3>\n
\n\n
\n -r<\/td>\n Returns search results in XML format. When this option is specified, the -c<\/span>, -f<\/span>, -i<\/span>, -p<\/span>, and -T<\/span> options are ignored<\/td>\n<\/tr>\n \n -c “field1, field2, … , fieldn”<\/td>\n Allows the user to provide a comma-separated list of fields to be displayed, as command line options. Field names must be identified using the fixed database names. If the -f<\/span> option is used in combination with the -c<\/span> option, all the fields included in myfile.txt<\/span> will be displayed in addition to the fields specified with the -c<\/span> option.When the -c<\/span> option is used, the file $HOME\/.evsearch<\/span> is ignored.Again, the fields selected must exist on the detailed report for the currently selected business area and project for the user<\/td>\n<\/tr>\n \n -f myfile.txt<\/td>\n Allows the user to specify a file that contains a list of all the fields to be displayed. The format of this file is identical to the format of the file $HOME\/.evsearch<\/span>, described above. When the -f<\/span> option is used, the file $HOME\/.evsearch<\/span> is ignored. As with the -c<\/span> option, the fields selected must exist on the detailed report for the currently selected business area and project for the user<\/td>\n<\/tr>\n \n -k “keyword1 keyword2 … keywordn”<\/td>\n Allows the user to provide a space-delimited list of keywords to search for. When performing a keyword search, all text fields in the issue are searched for occurrences of the keywords entered. When multiple keywords are entered, the search will return issues that match all of the keywords<\/td>\n<\/tr>\n \n -n<\/td>\n Causes the search to ignore case<\/td>\n<\/tr>\n \n -i<\/td>\n causes the search to use the ExtraView data dictionary names and list value names, as opposed to the data dictionary titles and the list titles for the search. For example, there is a data dictionary field named STATUS that may have a title of \u2018Status of Issue\u2019. This field may have as one of its values a name of NEW that has a title of \u2018Newly Submitted\u2019. The following searches are synonymous:<\/p>\n
\nevsearch ‘Status of Issue=Newly Submitted’ q<\/span><\/td>\n<\/tr>\n\n -l pagelength<\/td>\n causes the output to paginate pagelength records at a time. The default for pagelength is 10<\/td>\n<\/tr>\n \n -s skipcount<\/td>\n causes the output to skip over ‘skipcount-1’ issues, and begin the report starting with record number skipcount<\/td>\n<\/tr>\n \n -d<\/td>\n shows a list of available reports by Name (also referred to as Title), with their report ID\u2019s. The report ID\u2019s may be used with the \u2013p<\/span> option. When this flag is specified, all other flags are ignored<\/td>\n<\/tr>\n \n -p reportID<\/td>\n by default, evsearch can only retrieve field data for fields that are on the system-wide Detailed Report. This option allows the user to specify an alternate Report, from which field data may be selected<\/td>\n<\/tr>\n \n -T templatefile<\/td>\n allows the user to specify a server side template file to be used for formatting the output of the search.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n NOTES<\/h3>\n
\n
EXAMPLE 1<\/h3>\n
$ evsearch status=Open priority=\"Priority 1\" q
\n--------
\nID: 12449
\nPriority: Priority 1
\nTitle: SM crashes when TMX allocates address
\n--------
\nID: 12446
\nPriority: Priority 1
\nTitle: My phone does not work
\n--------
\nID: 12426
\nPriority: Priority 1
\nTitle: Lever arm broken
\n--------
\nID: 12424
\nPriority: Priority 1
\nTitle: new color scheme inconsistent
\n4 records found.
\n$<\/code><\/p>\nEXAMPLE 2<\/h3>\n
$ evsearch -r Status=Open q | evxmlc -c \"ID(8),ASSIGNED_TO(-13),SHORT_DESCR(-48)\"
\nDefect # Assigned\u00a0\u00a0\u00a0\u00a0\u00a0 Title
\n-------- ------------- ------------------------------------------------
\n10152 Don Powell\u00a0\u00a0\u00a0 User interface does not refresh before menu is displayed
\n10132 Don Powell\u00a0\u00a0\u00a0 On pressing the enter key on the home page, nothing happens
\n10120 Steve Hoydic\u00a0 Architecture Diagram Needs Review
\n10118 Jom Smith\u00a0\u00a0\u00a0\u00a0 There is a typo in the doc. On page 234
\n10108 Don Powell\u00a0\u00a0\u00a0 I found a problem with calculation on stairs
\n10105 Dave Green\u00a0\u00a0\u00a0 When the timer goes past zero, an error is generated
\n10034 Don Powell\u00a0\u00a0\u00a0 When you click on the Product edit box it throws an error <\/code><\/p>\n7 records processed.
\n$<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"