Category:Create a Tracker Issue (Pathway)
From Foss2Serve
(Difference between revisions)
(Created page with "__NOTOC__ '''The contributor will''': study and try to create a tracker issue (e.g. a bug report or feature request). '''The contribution is''': a new tracker issue to impr...") |
Darci.burdge (Talk | contribs) (→Prerequisites) |
||
(One intermediate revision by one user not shown) | |||
Line 18: | Line 18: | ||
* Describe issue trackers and how they are used. | * Describe issue trackers and how they are used. | ||
* Access the issue tracker with appropriate permissions. | * Access the issue tracker with appropriate permissions. | ||
− | |||
|- | |- | ||
| Community | | Community | ||
Line 43: | Line 42: | ||
:: i. For a bug report, describe the ''problem'', and how to reproduce it. | :: i. For a bug report, describe the ''problem'', and how to reproduce it. | ||
:: ii. For a feature request, describe the ''benefit'', and how it might work. | :: ii. For a feature request, describe the ''benefit'', and how it might work. | ||
− | :: iii. How many users are affected, and how important is it to them. | + | :: iii. For a complex issue, consider whether it should be split into several smaller issues. |
+ | :: iv. How many users are affected, and how important is it to them. | ||
: b. Describe actual or potential ''solution(s)'' to the issue. | : b. Describe actual or potential ''solution(s)'' to the issue. | ||
Line 49: | Line 49: | ||
:: ii. What code, documentation, database, etc would be changed? | :: ii. What code, documentation, database, etc would be changed? | ||
:: iii. How difficult would these changes be? | :: iii. How difficult would these changes be? | ||
+ | :: iv. For a complex solution, consider whether it should be split into several smaller issues. | ||
| You identified one or more aspects to be included. | | You identified one or more aspects to be included. |
Latest revision as of 23:58, 8 March 2017
The contributor will: study and try to create a tracker issue (e.g. a bug report or feature request).
The contribution is: a new tracker issue to improve the project.
Prerequisites
Area | The contributor must be able to: |
---|---|
Software Configuration |
|
Issue Tracker |
|
Community |
|
Pathway Steps, Outcomes, & Learning Activities
Follow the project’s policies and practices to complete the steps below.
Pathway Step | Step Outcome | Process Skills Focus | Related Learning Activities |
---|---|---|---|
1. Select a issue to create. For example, the issue might be:
|
You selected an issue. | ||
2. Study the issue details, and identify aspect(s) that should be included.
|
You identified one or more aspects to be included. | ||
3. Look for more information.
|
You have provided or asked for more information. | ||
4. Create the issue.
|
You created an issue in the issue tracker. |
Notes for Learning Activities Related to this Pathway
When creating activities:
- Use examples to demonstrate concepts to student.
- Use screen shots when possible.
This category currently contains no pages or media.