Changes between Version 2 and Version 3 of TracQuery

Dec 31, 2005, 4:43:10 PM (13 years ago)



  • TracQuery

    v2 v3  
    1 = チケットクエリ =
     1= Trac Ticket Queries =
    4 [wiki:TracReports レポート]に加えて、Tracは''カスタムチケットクエリ''をサポートしています。''カスタムチケットクエリ''は、ある一定の基準を満たすチケットのリストを表示するのに使用されます。
     4In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', used to display lists of tickets meeting a specified set of criteria.
    6 カスタムクエリを設定・実行するために、ナビゲーションバーの''チケットを見る''モジュールに切り替え、''カスタムクエリ''のリンクを選択します。
     6To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.
    8 == クエリフォーム ==
     8== Filters ==
     9When you first go to the query page the default filters will display all open tickets, or if you're logged in it will display open tickets assigned to you.  Current filters can be removed by clicking the button to the right with the minus sign on the label.  New filters are added from the pulldown list in the bottom-right corner of the filters box.  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria.
    10 フォームが表示されています。いろいろなチケットのプロパティ(組み込みとカスタムしたものの両方)の値を選択させたり、値を入力させるようになっています。このフォームで選択/入力された値は表示するチケットの一覧を絞り込むのに使用されます。基準を満たすチケットのみが表示されるのです。
     11You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.
    12 == 結果表示 ==
     13Once you've edited your filters click the ''Update'' button to refresh your results.
    14 検索の実行後、選択された基準を満たすチケットのリストが表示されます。デフォルトではリストは優先度でソートされています。ヘッダの列名をクリックすることによりソートの基準を変更することができます。同じヘッダを再びクリックすると、昇順/降順が変更されます。
     15== Navigating Tickets ==
     16Clicking on one of the query results will take you to that ticket.  You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Query'' link to return to the query page. 
    16 ''クエリの手直し''をクリックすると、クエリを編集することができます。
     18You can safely edit any of the tickets and continue to navigate through the results using the ''Next/Previous/Back to Query'' links after saving your results.  When you return to the query any tickets you edited will be displayed with italicized text.  If one of the tickets was edited such that it no longer matches the query criteria the text will also be greyed.  The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.
     20== Saving Queries ==
     22While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.
     24=== Using TracLinks ===
     26You may want to save some queries so that you can come back to them later.  You can do this by making a link to the query from any Wiki page.
     28[query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8]
     31Which is displayed as:
     32  [query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8]
     34This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).
     36Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
     38[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
     41Whis is displayed as:
     42  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
     44The advantage of this approach is that you can also specify the grouping and ordering, which is not possible using the first syntax.
     46=== Using the `[[TicketQuery]]` Macro ===
     48The `[[TicketQuery]]` macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
     55This is displayed as:
     56  [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
     58Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language].
     60A more compact representation without the ticket summaries is also available:
     62[[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
     65This is displayed as:
     66  [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
     68=== Query Language ===
     70`query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separate by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values.
     72The available operators are:
     73|| '''=''' || the field content exactly matches the one of the values ||
     74|| '''~=''' || the field content contains one or more of the values ||
     75|| '''!^=''' || the field content starts with one of the values ||
     76|| '''$=''' || the field content ends with one of the values ||
     78All of these operators can also be negated:
     79|| '''!=''' || the field content matches none of the values ||
     80|| '''!~=''' || the field content does not contain any of the values ||
     81|| '''!!^=''' || the field content does not start with any of the values ||
     82|| '''!$=''' || the field content does not end with any of the values ||
    19 参考: TracTickets, TracReports, TracGuide
     85See also: TracTickets, TracReports, TracGuide