Difference between revisions of "Workflow"
From Amahi Wiki
(Created page with "Our workflow is typically as follows, using the https://bugs.amahi.org = Status = Generally, the flow of the bugs' status is typically captured with this cru...") |
(→Status) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
New ==> [ Assigned <==> Feedback ] ==> Closed | New ==> [ Assigned <==> Feedback ] ==> Closed | ||
| − | * bugs start as '''New''' and | + | * bugs start as '''New''' and no one assigned. |
| − | * if at the time of creation or any time later you know who should take it, set it to '''Assigned''' and set the Assignee to the person who should work on it | + | * if at the time of creation or any time later you know who should take it, set it to '''Assigned''' and set the Assignee to the person who should work on it. |
| − | * if some question arises or more info is needed, set the bug to '''Feedback''' and set the assignee to the person who should provide the feedback or answer the question | + | * if some question arises or more info is needed, set the bug to '''Feedback''' and set the assignee to the person who should provide the feedback or answer the question if possible. |
| − | * the person answering should set the bug to '''Assigned''' and the assignee to the person working to fix the bug or implement the feature | + | * the person answering should set the bug to '''Assigned''' and the assignee to the person working to fix the bug or implement the feature. |
| − | * once the person working on it is done, it sets it to '''Feedback''' and assignee to the person who need to verify the issue | + | * once the person working on it is done, it sets it to '''Feedback''' and assignee to the person who need to verify the issue is corrected or feature implemented. |
| − | * if the issue verifies well, the person assigned sets it to '''Closed''' and it's all done | + | * if the issue verifies well, the person assigned sets it to '''Closed''' and it's all done. |
| − | * if not, then the bug should be set to '''Assigned''' and the assignee to the person working on it | + | * if not, then the bug should be set to '''Assigned''' and the assignee to the person working on it. |
| − | * if the issue is found to | + | * if the issue is found to reoccur, the bug is opened by setting it to '''Assigned''' and the assignee to the person working on it. |
=Priorities= | =Priorities= | ||
| − | * we list all bugs and features | + | * we list all bugs and features<sup>1</sup> as the default priority ('''Normal''') |
* what we need to work on at any given time should be set to '''High''' (the list of issues can be sorted by priority easily, to see things better) | * what we need to work on at any given time should be set to '''High''' (the list of issues can be sorted by priority easily, to see things better) | ||
* what we should work on *next* should be set to '''Medium''' priority | * what we should work on *next* should be set to '''Medium''' priority | ||
| Line 24: | Line 24: | ||
* once we get done with one item that is high priority, it gets set to closed | * once we get done with one item that is high priority, it gets set to closed | ||
| − | + | ||
| + | <sup>1</sup> we do not have a strong enforcement of bugs/features, at least at the moment | ||
Latest revision as of 23:31, 21 April 2014
Our workflow is typically as follows, using the https://bugs.amahi.org
Status
Generally, the flow of the bugs' status is typically captured with this crude diagram:
New ==> [ Assigned <==> Feedback ] ==> Closed
- bugs start as New and no one assigned.
- if at the time of creation or any time later you know who should take it, set it to Assigned and set the Assignee to the person who should work on it.
- if some question arises or more info is needed, set the bug to Feedback and set the assignee to the person who should provide the feedback or answer the question if possible.
- the person answering should set the bug to Assigned and the assignee to the person working to fix the bug or implement the feature.
- once the person working on it is done, it sets it to Feedback and assignee to the person who need to verify the issue is corrected or feature implemented.
- if the issue verifies well, the person assigned sets it to Closed and it's all done.
- if not, then the bug should be set to Assigned and the assignee to the person working on it.
- if the issue is found to reoccur, the bug is opened by setting it to Assigned and the assignee to the person working on it.
Priorities
- we list all bugs and features1 as the default priority (Normal)
- what we need to work on at any given time should be set to High (the list of issues can be sorted by priority easily, to see things better)
- what we should work on *next* should be set to Medium priority
- we work on what should be high/medium on weekly planning meetings or perhaps email, as needed
- once we get done with one item that is high priority, it gets set to closed
1 we do not have a strong enforcement of bugs/features, at least at the moment
