In this release we've redesigned and simplified tab area of BUGtrack.
Prefs tabs is now gone. To change personal preferences, click on your name in a top-right menu, it now serves as a link to preferences page.
Maximum size of custom Logo has been increased to 200x100. If you upload larger images, BUGtrack will resize it to fit to 200x100 box preserving image proportions
Search tab and Go to# box are now combined into single search box. Will you type digits, BUGtrack will navigate to an record by number. Will you type some letters, BUGtrack will search records containing the text specified.
Text search logic is also changed. Instead of specifying how to interpret text (All Words, Any Word, Exact Phrase), you can now write queries in a simple yet effective language. Remaining options: whether to search closed bugs and maximum number of records to display are available from drop-down menu
Text query language supports following constructs:
|feature||Searches for inflectional forms of the word feature.|
|feature failure |
feature AND failure
|Searches for inflectional forms of the words feature and failure. Keyword AND is optional. This is identical to former All Words option.|
|feature OR failure||Searches for inflectional forms of the words feature or failure. You can use either pipe symbol or OR keyword. This is identical to former Any Word option.|
|"feature failure"||Searches for exact phrase.|
|feature -failure||Searches for issues containing word feature but NOT the word failure|
|+feature||Exact word: searches for word feature without generating inflectional forms.|
|feat*||Prefix search: searches for words that starts with feat|
|<feature failure>||Searches for the word failure in close proximity to the word feature.|
- If you want to search for string of digits, prefix your text with double quote to avoid resolving text as record number.
- You can use & (ampersand) symbol instead of AND keyword and | (pipe) symbol instead of OR keyword.
- AND operator takes precedence over OR in queries. You can change the precedence using parentheses. For example:
feature failure OR issue
is evaluated as
(feature AND failure) OR issue
You can change the order of evaluation so that OR evaluated first:
feature (failure OR issue)
- Certain combinations are not allowed. For example you can not write the query consisting solely of NOT constructs or containing OR NOT combinations or use prefix search or exact word search in proximity brackets. As we designed search process to be unobtrusive, such invalid constructs are silently ignored.