Redmine configurations » History » Version 20
scarabeus_iv, 2013-08-07 09:15
Markdownify
| 1 | 20 | ||
|---|---|---|---|
| 2 | ><p>{{>toc}}</p> |
||
| 3 | |||
| 4 | General settings |
||
| 5 | ================ |
||
| 6 | |||
| 7 | Projects |
||
| 8 | ======== |
||
| 9 | |||
| 10 | Roles and Workflow |
||
| 11 | ================== |
||
| 12 | |||
| 13 | No customization has been set up for roles. The original workflow has been slightly modified. In general, developers permissions has been increased and Non members permissions has been reduced. |
||
| 14 | |||
| 15 | Issues |
||
| 16 | ====== |
||
| 17 | |||
| 18 | These are the topics that are not self explained. |
||
| 19 | |||
| 20 | Tracker |
||
| 21 | ------- |
||
| 22 | |||
| 23 | The following trackers (type of tasks) have been globally configured in Redmine: |
||
| 24 | |||
| 25 | * action: what we commonly recognize as task |
||
| 26 | * analysis: evaluation, analysis, study of a situation, a problem... |
||
| 27 | * coordination: management, meetings, etc. |
||
| 28 | * communication: marketing, discussions, talks, presentations, conferences, social community work |
||
| 29 | * report: elaborate, develop and present reports, conclusions, etc. |
||
| 30 | |||
| 31 | They can be disable for each project. New ones can be created for each project too. |
||
| 32 | |||
| 33 | Priority |
||
| 34 | -------- |
||
| 35 | |||
| 36 | * Immediate: Crisis, drop everything |
||
| 37 | * Urgent: On our way to crisis. The controller or manager should know about this. |
||
| 38 | * High: somebody needs this to be done, please work on it as soon as possible. |
||
| 39 | * Normal: default state of tasks. Work on it. |
||
| 40 | * Low: Nice to have but we can skip it. Work on it if you have time. |
||
| 41 | |||
| 42 | Status |
||
| 43 | ------ |
||
| 44 | |||
| 45 | The status of any task are: |
||
| 46 | |||
| 47 | * New: the task is created but nobody is working on it. |
||
| 48 | * In progress: the task is being done by somebody. The task must reflect the percentage of the task that is done. |
||
| 49 | * Feedback: the task is done but somebody is checking it. The task needs that somebody else check that the partial work done so far is accurate. The task needs information (not action) from somebody to keep going). |
||
| 50 | * Resolved: the task is done. |
||
| 51 | * Closed: the controller verifies that the task is done, and the percentage and spend time is filled and correct. |
||
| 52 | * Rejected: the assigned person send d back the task to the author for the reasons below. The rejection must be clearly justified. |
||
| 53 | * Is not able to do it |
||
| 54 | * Is not the right person to do it |
||
| 55 | * Thinks that the task do not need to be done. |
||
| 56 | * Do not agree with the conditions or information related to the task. |
||
| 57 | |||
| 58 | Documents, files and repository |
||
| 59 | =============================== |
||
| 60 | |||
| 61 | Roadmap |
||
| 62 | ======= |
||
| 63 | |||
| 64 | The release process has been divided into the common milestones. For the generic Release process project, the dates are not accurate for each milestone. They are for the 12.3 Release process project and the following ones. These milestones needs to be configured for each subproject, since the dates and number of milestones might vary from release to release. |
||
| 65 | |||
| 66 | The configuration of the milestones are a key step to organize the tasks (issues), visualize them in the roadmap, calendar and Gantt diagram. |
||
| 67 | |||
| 68 | Time entries |
||
| 69 | ============ |