Category talk:Create a Tracker Issue (Pathway)
Darci.burdge (Talk | contribs) |
Darci.burdge (Talk | contribs) |
||
| Line 4: | Line 4: | ||
The only way you can create a tracker issue for a bug is if you've discovered a bug while using the project. | 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: Determine if this bug has already been identified. | ||
| + | |||
| + | Step 3: If it has not, then: | ||
Revision as of 00:18, 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: Determine if this bug has already been identified.
Step 3: If it has not, then:
