Evaluation of a Tracker Issue
When a tracker issue is created and assigned a module, it must be evaluated and possibly handled by the [:Process_Role/Module_Owner: Module Owner].
Purpose
To have new tracker issues evaluated adn possibly fixed as quick as possible
Responsible
[:Process_Role/Module_Owner: Module Owner]. Please refer to [:Development/Staffing: Staffing] for overview of modules, owneers and backups.
Method
Find tracker issues for module via the [https://gforge.statsbiblioteket.dk/tracker/?group_id=7 trackers in GForge]
- Check if the tracker issue is assigned to the right module.
- If the tracker issue shoud be assigned to another known module do following
- Change the 'Module' field to what seems the right module
- Change the 'Assigned To' field to the owner of this module.
- If appropriate make a comment on the reason of the change in the 'OR Attach A Comment' field.
- If the tracker issue shoud be assigned to another NOT known module do following
- Change the 'Module' field to "None"
- Change the 'Assigned To' field to the name of the [:Process_Role/QA_Coordinator: QA Coordinator].
- If appropriate make a comment on the reason of the change in the 'OR Attach A Comment' field.
Only proceed with issues for actual module
- Set priority according to how important the tracker issue seem to be.
If the priority is set to the highest priority (5) then contact [:Process_Role/QA_Coordinator: QA Coordinator] who will take action according to the [:Process/Prioritization:Prioritization] process.
Only proceed with issues with priority is less than 5
- If we currently do NOT have a code freeze at evaluation time
- If there is an easy solution to fix the tracker issue (guideline maximum 1 md.):
- Set Status to "In Progress"
Follow the [:Process/Implematation:Implementation] process
- If there is a little more complex solution to fix the tracker issue:
- Make a description of how the tracker issue should be fixed in the 'OR Attach A Comment' field
- Write and estimate (with uncertaincy description if appropriate) of the fix
- Set Status to "Evaluated"
- If there is an easy solution to fix the tracker issue (guideline maximum 1 md.):
- If we currently DO have a code freeze at evaluation time
- Evaluate if the tracker issue should be fixed before release.
- If it should be fixed before release then
- Contact [:Process_Role/QA_Coordinator: QA Coordinator] and [:Process_Role/Test_Coordinator: Test Coordinator].
- If it should NOT be fixed before release then
- Evaluate the tracker issue after codefreeze
Time
Every time a new tracker issue is created.
The reaction time on evaluation of a tracker issue should be no more than a week.
All tracker issues must be evaluated or fixed before [:Process/Code_Freeze:Code Freeze].
Input
Tracker issue that has been assigned to a specific module (set by creater of issue or in the [:Process/Monitoring_Trackers:Monitoring Trackers] process
Output
Evaluated or fix in progress of tracker issue
Comments and suggestions for improvements
None.