Commit bb704999 authored by Sunil Joshi's avatar Sunil Joshi Committed by Frédéric Buclin

Bug 363910: "Add a new query" should be renamed

r/a=LpSolit
parent 12e5d51d
...@@ -1922,7 +1922,7 @@ ...@@ -1922,7 +1922,7 @@
<para> <para>
Each whining event is associated with zero or more schedules. A Each whining event is associated with zero or more schedules. A
schedule is used to specify when the query (specified below) is to be schedule is used to specify when the search (specified below) is to be
run. A new event starts out with no schedules (which means it will run. A new event starts out with no schedules (which means it will
never run, as it is not scheduled to run). To add a schedule, press never run, as it is not scheduled to run). To add a schedule, press
the "Add a new schedule" button. the "Add a new schedule" button.
...@@ -1981,7 +1981,7 @@ ...@@ -1981,7 +1981,7 @@
is any saved search to be run as part of the specified schedule (see is any saved search to be run as part of the specified schedule (see
above). You start out without any searches associated with the event above). You start out without any searches associated with the event
(which means that the event will not run, as there will never be any (which means that the event will not run, as there will never be any
results to return). To add a search, press the "Include search" button. results to return). To add a search, press the "Add a search" button.
</para> </para>
<para> <para>
...@@ -2004,29 +2004,29 @@ ...@@ -2004,29 +2004,29 @@
<note> <note>
<para> <para>
When running queries, the whining system acts as if you are the user When running searches, the whining system acts as if you are the user
executing the query. This means that the whining system will ignore executing the search. This means that the whining system will ignore
bugs that match your query, but that you cannot access. bugs that match your search, but that you cannot access.
</para> </para>
</note> </note>
<para> <para>
Once you have chosen the saved search to be executed, give the query a Once you have chosen the saved search to be executed, give the search a
descriptive title. This title will appear in the email, above the descriptive title. This title will appear in the email, above the
results of the query. If you choose "One message per bug", the query results of the search. If you choose "One message per bug", the search
title will appear at the top of each email that contains a bug matching title will appear at the top of each email that contains a bug matching
your query. your search.
</para> </para>
<para> <para>
Finally, decide if the results of the query should be sent in a single Finally, decide if the results of the search should be sent in a single
email, or if each bug should appear in its own email. email, or if each bug should appear in its own email.
</para> </para>
<warning> <warning>
<para> <para>
Think carefully before checking the "One message per bug" box. If Think carefully before checking the "One message per bug" box. If
you create a query that matches thousands of bugs, you will receive you create a search that matches thousands of bugs, you will receive
thousands of emails! thousands of emails!
</para> </para>
</warning> </warning>
...@@ -2037,7 +2037,7 @@ ...@@ -2037,7 +2037,7 @@
<para> <para>
Once you have defined at least one schedule, and created at least one Once you have defined at least one schedule, and created at least one
query, go ahead and "Update/Commit". This will save your Event and make search, go ahead and "Update/Commit". This will save your Event and make
it available for immediate execution. it available for immediate execution.
</para> </para>
......
...@@ -27,7 +27,7 @@ ...@@ -27,7 +27,7 @@
%] %]
<p> <p>
"Whining" is when [% terms.Bugzilla %] executes a saved query at a regular interval "Whining" is when [% terms.Bugzilla %] executes a saved search at a regular interval
and sends the resulting list of [% terms.bugs %] via email. and sends the resulting list of [% terms.bugs %] via email.
</p> </p>
...@@ -48,8 +48,8 @@ ...@@ -48,8 +48,8 @@
<p> <p>
Searches come from saved searches, which are created by executing a <a Searches come from saved searches, which are created by executing a <a
href="query.cgi">search</a>, then telling [% terms.Bugzilla %] to remember href="query.cgi">search</a>, then telling [% terms.Bugzilla %] to remember
the search under a particular name. Add a query by clicking "Add a new the search under a particular name. Add a search by clicking "Add a
query", and select the desired saved search name under "Search" and add a search", and select the desired saved search name under "Search" and add a
title for the [% terms.bug %] table. The optional number entered under title for the [% terms.bug %] table. The optional number entered under
"Sort" will determine the execution order (lowest to highest) if multiple "Sort" will determine the execution order (lowest to highest) if multiple
queries are listed. If you check "One message per [% terms.bug %]," each [% queries are listed. If you check "One message per [% terms.bug %]," each [%
...@@ -216,7 +216,7 @@ ...@@ -216,7 +216,7 @@
</td> </td>
<td align="left"> <td align="left">
No searches <br> No searches <br>
<input type="submit" value="Add a new query" <input type="submit" value="Add a search"
name="add_query_[% event.key %]" name="add_query_[% event.key %]"
id="add_query_[% event.key %]"> id="add_query_[% event.key %]">
</td> </td>
...@@ -282,7 +282,7 @@ ...@@ -282,7 +282,7 @@
<tr> <tr>
<td colspan="3"> <td colspan="3">
<input type="submit" value="Add a new query" <input type="submit" value="Add a search"
name="add_query_[% event.key %]" name="add_query_[% event.key %]"
id="add_query_[% event.key %]"> id="add_query_[% event.key %]">
</td> </td>
...@@ -322,7 +322,7 @@ ...@@ -322,7 +322,7 @@
</select> </select>
[% ELSE %] [% ELSE %]
Please visit the <a href="query.cgi">Search</a> page and save a query Please visit the <a href="query.cgi">Search</a> page and save a search
[% END %] [% END %]
[%+ END %] [%+ END %]
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment