diff options
Diffstat (limited to 'docs/en/xml/using.xml')
| -rw-r--r-- | docs/en/xml/using.xml | 20 |
1 files changed, 6 insertions, 14 deletions
diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml index e625cca16..f91695c59 100644 --- a/docs/en/xml/using.xml +++ b/docs/en/xml/using.xml @@ -801,17 +801,11 @@ <title>Adding/removing tags to/from bugs</title> <para> You can add and remove tags from individual bugs, which let you find and - manage them more easily. Creating a new tag automatically generates a saved - search - whose name is the name of the tag - which lists bugs with this tag. - This saved search will be displayed in the footer of pages by default, as - all other saved searches. The main difference between tags and normal saved - searches is that saved searches, as described in the previous section, are - stored in the form of a list of matching criteria, while the saved search - generated by tags is a list of bug numbers. Consequently, you can easily - edit this list by either adding or removing tags from bugs. To enable this - feature, you have to turn on the <quote>Enable tags for bugs</quote> user - preference, see <xref linkend="userpreferences" />. This feature is disabled - by default. + manage bugs more easily. Tags are per-user and so are only visible and editable + by the user who created them. You can then run queries using tags as a criteria, + either by using the Advanced Search form, or simply by typing "tag:my_tag_name" + in the QuickSearch box at the top (or bottom) of the page. Tags can also be + displayed in buglists. </para> <para> @@ -820,9 +814,7 @@ these bugs and mixing all these reasons, you can now store these bugs in separate lists, e.g. <quote>Keep in mind</quote>, <quote>Interesting bugs</quote>, or <quote>Triage</quote>. One big advantage of this way to manage bugs - is that you can easily add or remove bugs one by one, which is not - possible to do with saved searches without having to edit the search - criteria again. + is that you can easily add or remove tags from bugs one by one. </para> </section> </section> |