summaryrefslogtreecommitdiffstats
path: root/docs/en/rst/using
diff options
context:
space:
mode:
Diffstat (limited to 'docs/en/rst/using')
-rw-r--r--docs/en/rst/using/finding.rst10
-rw-r--r--docs/en/rst/using/tips.rst6
2 files changed, 0 insertions, 16 deletions
diff --git a/docs/en/rst/using/finding.rst b/docs/en/rst/using/finding.rst
index 414e30cba..515f2e37d 100644
--- a/docs/en/rst/using/finding.rst
+++ b/docs/en/rst/using/finding.rst
@@ -33,10 +33,6 @@ would search only in that product.
You can also use it to go directly to a bug by entering its number or its
alias.
-.. todo:: Need to incorporate the full reference, and link it properly from
- the GUI. https://bugzilla.mozilla.org/page.cgi?id=quicksearch.html
- Turn this item into a bug after checkin.
-
Simple Search
=============
@@ -101,9 +97,6 @@ There are three fields in each row of a boolean search.
Multiple Charts
---------------
-.. todo:: This needs rewriting for the new UI.
- Turn this item into a bug after checkin.
-
The terms within a single row of a boolean chart are all
constraints on a single piece of data. If you are looking for
a bug that has two different people cc'd on it, then you need
@@ -248,9 +241,6 @@ Remember Search As:
Adding and Removing Tags on Bugs
================================
-.. todo:: Looks like you can no longer do this from search results; is that right?
- Turn this item into a bug after checkin.
-
You can add and remove tags from individual bugs, which let you find and
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,
diff --git a/docs/en/rst/using/tips.rst b/docs/en/rst/using/tips.rst
index a48149275..411d457fd 100644
--- a/docs/en/rst/using/tips.rst
+++ b/docs/en/rst/using/tips.rst
@@ -79,12 +79,6 @@ reference on supported Markdown structures, please see the
`syntax help <https://bugzilla.mozilla.org/page.cgi?id=markdown.html>`_ link
next to the Markdown checkbox for new comments.
-.. todo:: The above link isn't ideal, but we can't easily link to the user's
- Bugzilla because the docs aren't always on a Bugzilla (e.g.
- when they are on ReadTheDocs). Best solution is to port the
- Markdown guide to ReST.
- Turn this item into a bug after checkin.
-
To use the Markdown feature, make sure that :guilabel:`Enable Markdown
support for comments` is set to :guilabel:`on`
in your :ref:`user-preferences` and that you also check the :guilabel:`Use