| 41 | Skeleton of PLATFORM_STANDARDS_MANUAL_TESTS/Bugs |
| 42 | Bugs are described and fixed in tickets |
| 43 | * Analysis of bugs: Reporting an issue is the analysis of the bug |
| 44 | * Summary: |
| 45 | * ''May start with "Crash:", "Tweak", "Unexpected behavior:". Crash means that the report form is evoked. Error report is needed as an attachment'' |
| 46 | * ''"TLID:" testlink id, if the bug can be reproduced by executing a testcase'' |
| 47 | * Short summary, custom text, what exactly happens in few words |
| 48 | * Type: bug |
| 49 | * Priority: determine the priority of the bug. |
| 50 | * ''Keywords - fill in related keywords, for example "text"'' |
| 51 | * ''Components - fill in component if you can determine the component'' |
| 52 | * reporter: devid , automatically added by trac |
| 53 | * Milestone - current milestone |
| 54 | * ''cc: a reminder to someone'' |
| 55 | * Analysis_owners: your devid |
| 56 | When you create the ticket, move it's status to analysis finished. |
| 57 | |
| 58 | |