[[BackLinksMenu]]

[[TicketQuery(summary=SCS_ISSUE_TRACKER_MAINTENANCE_R4, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]]

= Analysis =
== Overview ==
Keeps tickets healthy.

== Task requirements ==
 * Review custom fields of the tickets (see Implementation idea)
 * Fill in custom information where possible (about owners and reviewers)
 * Send notification to people that miss this information.

== Task result ==
Custom fields with proper content for iterations 2+

== Implementation idea ==
[wiki:SCS_ISSUE_TRACKER_MAINTENANCE] contains queries that do the following: for each task state are shown the needed custom fields with their content. You may modify the queries not to show iteration1 if you decide there is no time for adding them. All you have to do is to add contents to the empty spaces.

== Related ==
[wiki:SCS_ISSUE_TRACKER_MAINTENANCE_R3][[BR]]
[wiki:SCS_ISSUE_TRACKER_MAINTENANCE_R2][[BR]]
== How to demo ==
Show the page with no blanks. [wiki:SCS_ISSUE_TRACKER_MAINTENANCE_R4]
= Design =
 * The analysis is old, but the requirements are reasonable
 * Use of "cc" was discussed for sending reminders to team members
  * Installed ticketbox plugin to show boxes with tickets that need attention (depending on username). A yellow box shows which tickets has the username in it's cc field. This is done in [report:18] and the following in the iteration page [wiki:ITERATION_07]
{{{
[[TicketBox({18},"Reminders",background=#FFCC33,summary,inline)]]
}}}
 * cc usage is not well defined, it just eases the communication between members via trac
 * The following report shows needed custom fields of the tickets in groups [report:21]
  * owners fields
  * reviewers fields
  * status
  * cc
 * Import plugin was installed. It allows importing tickets from csv file (trac can export reports in this format). When the ticket id already exists, the ticket is changed.
 * In later revisions a script that updates automatically custom fields of groups will be designed
 * In implementation section create a list with all tickets and see where there are problems
  * The report may not contain tickets with status new
  * The report should contain the ''following fields: ticket#, summary, *owners, *reviewers, *score, cc''
  * Tickets with non-filled owners field. This will be easy if the report is ''sorted by status''
 * Export the report as CSV (bottom of the trac page), open it in Open Office and resolve problems where possible
  * if the report is arranged properly, you will see blanks where a custom field is missed
 * For the tickets that you are not sure who is the *owner, add yourself as cc and resolve them manually later
 * Save the CSV and import it using Import tab in trac
= Implementation =
 * For grouped tickets [report:21] is used for the csv report. Blanks were filled for each group. The CSV was imported again.
 * This [http://sophie2.org/trac/query?status=s1a_analysis_started&status=s1b_analysis_finished&status=s1c_analysis_ok&status=s2a_design_started&status=s2b_design_finished&status=s2c_design_ok&status=s3a_implementation_started&status=s3b_implementation_finished&status=s3c_implementation_ok&status=s4a_test_started&status=s4b_test_finished&status=s4c_test_ok&col=id&col=summary&col=status&col=ticket_group&col=importance&col=effort&col=analysis_owners&col=design_owners&col=implementation_owners&col=test_owners&col=analysis_reviewers&col=design_reviewers&col=implementation_reviewers&col=test_reviewers&col=analysis_score&col=design_score&col=implementation_score&col=test_score&col=cc&order=status query] is used for the csv export. All tickets were fixed (excluding these from iteration 1) and reminders were sent where needed.
= Testing =
^(Place the testing results here.)^

= Comments =
^(Write comments for this or later revisions here.)