Category talk:Create a Tracker Issue (Pathway)

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
Would like others thoughts on whether the pathway should include a step to understand a bug tracker or should this be per-requisite knowledge.
 
Would like others thoughts on whether the pathway should include a step to understand a bug tracker or should this be per-requisite knowledge.
  
The prerequisites should not include create, update, and a
+
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.

Revision as of 00:08, 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.

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox