バージョン 3 から バージョン 4 における更新: TracDoc/QueryChart/En

更新日時:

2008/12/06 15:56:53 (16 年 前)

更新者:

hirobe (IP アドレス: 133.6.203.10)

コメント:

--

TracDoc/QueryChart/En

@@ -1 +1 @@
 = Query Chart macro that draws in bug settling curve and Barndaunchart =
 == Description ==
-This is Wiki macro that counts the number of tickets, and draws in the bug settling curve and    [[BR]]Barndaunchart.
+This is Wiki macro that counts the number of tickets, and draws in the bug settling curve and Barndaunchart.
 
 Progress can be displayed good-looking by it not only puts on Wiki because it is Wiki macro but also displaying it with the time line and the report.
@@ -7 +7 @@
 Moreover, the function to preserve in the custom field is bundled to this plug-in on the day when the status of the ticket changed. The day when the ticket closed can be made a graph by combining this with the graph.
 
+
 == ScreenShot ==
-[[Image(http://weekbuild.sakura.ne.jp/trac/raw-attachment/wiki/TracDoc/QueryChart/screenshot.png)]]
+[[Image(wiki:TracDoc/QueryChart:screenshot.png)]]
 
 == Requament ==
@@ -39 +40 @@
 
  * query: Search condition of ticket. The following three kinds of can be described.
-   * [http://trac.edgewall.org/wiki/TracQuery#QueryLanguage Query language] notation of TicketQuery macro:      [[BR]]Write the condition without applying ? to the head. Refer to the [http://trac.edgewall.org/wiki/TracQuery#QueryLanguage Query language] for details.      [[BR]]!query:status=new|assigned&version;^=1.0
-   * Notation displayed in URL with custom query：      [[BR]]Write conditions delimited by & applying ?(Without forgetting :) to the head as follows. It might be good to put the part of URL specifying the condition on the screen of custom query.      [[BR]]!query:?status=new&status;=assigned&version;=^1.0
-   * Omitte：      [[BR]]It is possible to omit it only when putting it on the column the explanation of the report made from custom query (which displayed in address field of a browser). It becomes a search condition specified the omission on the screen. Please omit this item (query:…) when omitting it.
- * col: Targeted item. Please describe by col=xxx, col=yyy, and switching off the comma district when you specify the plural. The item name can specify both the field name (name of the field in Trac) and the label (displayed item name).
+   * [http://trac.edgewall.org/wiki/TracQuery#QueryLanguage Query language] notation of TicketQuery macro:[[BR]]
+     Write the condition without applying ? to the head. 
+     Refer to the [http://trac.edgewall.org/wiki/TracQuery#QueryLanguage Query language] for details.[[BR]]
+     !query:status=new|assigned&version;^=1.0
+   * Notation displayed in URL with custom query:[[BR]]
+     Write conditions delimited by & applying ? (Without forgetting :) to the head as follows. It might be 
+     good to put the part of URL specifying the condition on the screen of custom query.[[BR]]
+     !query:?status=new&status;=assigned&version;=^1.0
+   * Omitte:[[BR]]
+     It is possible to omit it only when putting it on the column the explanation of the report made from 
+     custom query (which displayed in address field of a browser). It becomes a search condition specified the 
+     omission on the screen. Please omit this item (query:...) when omitting it.
+ * col: Targeted item. Please describe by col=xxx, col=yyy, and switching off the comma district when you 
+   specify the plural. The item name can specify both the field name (name of the field in Trac) and the label 
+   (displayed item name).
  * per:(=day,week,free) Unit of total. Default is week.
  * start: Day in left end of graph. If it is unspecification, it is the most past day of the ticket. yyyy/mm/dd form
@@ -49 +61 @@
  * height: Height of graph. It specifies it by the unit of px. If it is unspecification,    [[BR]]it is 300px.
  * upper: The improvement chart is written (bug settling curve etc.). Down chart when not specifying it.
+
 Example：
 
@@ -60 +73 @@
 It is necessary to decide the rule like "This day is assumed to be a completion day" in Trac because customizing the work flow is possible since Trac0.11 in addition to possible sending back the closing ticket. In this plug-in, "Generation order of status" is decided and the date is set according to it. The date is set in the custom field so that the generation order should not become low status from the one with high generation order ahead.
 
-In the work flow of default, I think that it goes well roughly by the following priority levels. (By the way, because the date of the ticket enters the item named time even if the custom field is not prepared, it is unnecessary  )
+In the work flow of default, I think that it goes well roughly by the following priority levels. (By the way, because the date of the ticket enters the item named time even if the custom field is not prepared, it is unnecessary  )
 
 (1)assigned (2)accepted (3)reopened (4)closed
@@ -66 +79 @@
 For instance, it is assumed that close was suddenly done to 12/10 after assign is done to 12/01 as follows. In this case, the date of the same 12/10 as closed is set in accepted and reopened whose generation order is higher than closed. In addition, it is assumed that reopen was done to 12/20 afterwards. Closed whose generation order is lower than reopened is cleared to empty.
 
-|| ||assigned||accepted||reopened||closed ||
+|| ||assigned||accepted||reopened||closed ||
 ||Assigned at 12/01||2008/12/01||-||-||- ||
 ||Afterwards, closed at 12/10||2008/12/01||2008/12/10||2008/12/10||2008/12/10 ||