Category talk:Create a Tracker Issue (Pathway)

Revision as of 00:37, 9 March 2017

Would like others thoughts on whether the pathway should include a step to understand a bug tracker or should this be per-requisite knowledge.

There is an Add a Feature Pathway...how is that different than create a tracker issue? Can't a tracker issue be reporting a bug OR creating a issue for a new feature. We really need two different pathways: one to create a tracker issue for a bug and create a tracker issue for a new feature.

The only way you can create a tracker issue for a bug is if you've discovered a bug while using the project.

Step 1: Somehow, someway a bug has been detected. You need to record anything you know about how you came to this error...screenshots, error message, anything you can remember about the steps that got you to this point.

Step 2: Make sure that you have installed all patches and updates.

Step 3: Determine if this bug has already been identified.

Step 4: If it has not, then: a) Is this really one issue or multiple issues b) Reproduce the bug and record any additional information gathered during this process c) Go to the community and determine how they handle bug reporting. If you are at the stage of creating a new issue, you will be required to follow any procedures they have in place

A good activity would be to have students do a walk-through of at least two communities guidelines on what to include in a good bug report, list similarities, differences, anything you find confusing. A table for them to fill in would be great.