Mercurial > p > roundup > code
comparison doc/user_guide.txt @ 6638:e1588ae185dc issue2550923_computed_property
merge from default branch. Fix travis.ci so CI builds don't error out
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Thu, 21 Apr 2022 16:54:17 -0400 |
| parents | 2eec7a500333 |
| children | e7b4ad2c57ac |
comparison
equal
deleted
inserted
replaced
| 6508:85db90cc1705 | 6638:e1588ae185dc |
|---|---|
| 1 .. meta:: | |
| 2 :description language=en: | |
| 3 Describes how to interact with and use a tracker with the | |
| 4 Roundup Issue Tracker. | |
| 5 | |
| 1 ========== | 6 ========== |
| 2 User Guide | 7 User Guide |
| 3 ========== | 8 ========== |
| 4 | 9 |
| 5 .. contents:: | 10 .. contents:: |
| 368 @group=priority,-status& | 373 @group=priority,-status& |
| 369 @sort=-activity& | 374 @sort=-activity& |
| 370 @filters=status,keyword& | 375 @filters=status,keyword& |
| 371 @columns=title,status,fixer | 376 @columns=title,status,fixer |
| 372 | 377 |
| 378 Full text search using the xapian, whoosh and native indexers treats | |
| 379 the search query as a series of space separated words. Any word less | |
| 380 than 2 characters or more than 50 characters is discarded. Also a | |
| 381 stoplist is used to remove common words like "with", "and" | |
| 382 etc. Additional stoplist words can be added in the tracker's | |
| 383 config.ini file. Once filtering of the word list is done, each indexed | |
| 384 item (e.g. title, file or message content ...) is searched and if all | |
| 385 the terms are found in the item the item is returned. Then the items | |
| 386 are mapped to an issue and the list of matching issues is generated. | |
| 387 | |
| 388 Other searching backends such as native-fts can be used in which case | |
| 389 the filtering above is not used. The search query can support | |
| 390 structure such as quoted phrases, matching one term or another rather | |
| 391 than both (or search), prefixes etc. In this case you should look at | |
| 392 the `documentation for configuring the native-fts`_ backend to find | |
| 393 the supported format and features. | |
| 394 | |
| 395 .. _`documentation for configuring the native-fts`: admin_guide.html#configuring-native-fts-full-text-search | |
| 373 | 396 |
| 374 Access Controls | 397 Access Controls |
| 375 --------------- | 398 --------------- |
| 376 | 399 |
| 377 User access is controlled through Permissions. These are are grouped | 400 User access is controlled through Permissions. These are are grouped |