| 55 | | Issues are linked with components where possible. |
| | 55 | * Issues are linked with components where possible. |
| | 56 | * The Owner of the ticket will be the one analyzing it, since proper analysis is the most important part. |
| | 57 | * We'll not use Severities. |
| | 58 | * Priorities will be set manually when analyzing the sprint. |
| | 59 | * In [wiki:SCS_ISSUE_TRACKER_MAINTENANCE_R1] will be nice to implement a better ticket workflow. Following the standard from the wiki task pages, i.e. Analysis, Design, Implementation, Testing, Done phase. In the description of the task ticket can be included the log for the task. |
