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

  1. Find tracker issues for module via the https://gforge.statsbiblioteket.dk/tracker/?group_id=7:trackers in GForge

  2. Check if the tracker issue is assigned to the right module.
  3. If the tracker issue shoud be assigned to another known module do following
    1. Change the 'Module' field to what seems the right module
    2. Change the 'Assigned To' field to the owner of this module.
    3. If appropriate make a comment on the reason of the change in the 'OR Attach A Comment' field.
  4. If the tracker issue shoud be assigned to another NOT known module do following
    1. Change the 'Module' field to "None"
    2. Change the 'Assigned To' field to the name of the [:Process_Role/QA_Coordinator: QA Coordinator].
    3. 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

  1. Set priority according to how important the tracker issue seem to be.

  2. If the priority is set to the highest priority (5) then inform [: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

  1. If there is an easy solution to fix the tracker issue (guideline maximum 1 md.):
    1. Set Status to "In Progress"

    2. Follow the [:Process/Implematation:Implementation] process

  2. If there is a little more complex solution to fix the tracker issue:
    1. Make a description of how the tracker issue should be fixed in the 'OR Attach A Comment' field
    2. Write and estimate (with uncertaincy factor if appropriate) of the fix
  3. Set Status to "Evaluated"

2. If it is indeed the right component, do we currently have code freeze? 2. It we have code freeze, evaluate if the bug should be fixed before release. 1. If so, contact QA and releasetest-coordinator. 2. If not, Evaluate the bug after codefreeze after the rules in step 1.2.1

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.