| | 1 | [[BackLinksMenu]] |
| | 2 | = Analysis = |
| | 3 | This task includes maintaining the issue tracker. |
| | 4 | |
| | 5 | == Overview == |
| | 6 | * Maintain the issue tracker regularly; |
| | 7 | * Delete, fix, group, etc - tickets. |
| | 8 | * Make sure tickets are up to date and generally correct. |
| | 9 | * Define and create useful Reports; |
| | 10 | * Review existing tickets. |
| | 11 | * Look for duplicate issues and remove them. |
| | 12 | * Look for unassigned tickets and assign them. |
| | 13 | * Send reminders to owners of tickets without progress (look for comments that contain "estimate" "this will be fixes after" "this can't be fixed" etc.) |
| | 14 | * Notify the team if the count of non-closed tickets is huge (in process of work we should consider what "huge count of tickets" mean. |
| | 15 | * Notify the team for other issues you consider abnormal. |
| | 16 | |
| | 17 | == Task requirements == |
| | 18 | * Issue Tracker should be well organized. |
| | 19 | * Issue tracker should be up-to-date. |
| | 20 | * Issue tracker should be fully consistent. |
| | 21 | |
| | 22 | == Task Result == |
| | 23 | * An easily maintainable tracker. |
| | 24 | |
| | 25 | == Implementation idea == |
| | 26 | * Review all reports. |
| | 27 | * Review all tickets. |
| | 28 | * Review owners of tasks. |
| | 29 | * Review components. |
| | 30 | * Create Severities. |
| | 31 | |
| | 32 | == How to demo == |
| | 33 | * Open http://asteasolutions.net:7080/sophie2 |
| | 34 | * Click on 'View Tickets' in the main tab-bar. |
| | 35 | * Use reports to browse reports. |
| | 36 | * Explain the different reports. |
| | 37 | |
| | 38 | = Design = |
| | 39 | Check the Overview requirements. |
| | 40 | * Review all reports. |
| | 41 | * Review all tickets. |
| | 42 | * Review owners of tasks. |
| | 43 | * Review components. |
| | 44 | * Create Severities. |
| | 45 | |
| | 46 | = Implementation = |
| | 47 | = Testing = |
| | 48 | = Log = |
| | 49 | [[Include(wiki:SCS_ISSUE_TRACKER_MAINTAINCE_R0_LOG)]] |
