PtBRRedmineIssueTrackingSetup » History » Version 1

Pedro Moritz de Carvalho Neto, 2015-07-27 21:52

1 1 Pedro Moritz de Carvalho Neto
h1. Issue tracking system
2 1 Pedro Moritz de Carvalho Neto
3 1 Pedro Moritz de Carvalho Neto
!>tracker_config.jpg!
4 1 Pedro Moritz de Carvalho Neto
5 1 Pedro Moritz de Carvalho Neto
h2. Trackers
6 1 Pedro Moritz de Carvalho Neto
7 1 Pedro Moritz de Carvalho Neto
Trackers are how you split your issues into different types - common ones are Bug, Feature, Defect or etc.
8 1 Pedro Moritz de Carvalho Neto
9 1 Pedro Moritz de Carvalho Neto
For each tracker, you can define: (see image right)
10 1 Pedro Moritz de Carvalho Neto
* Name  (the example pictured is 'Bug')
11 1 Pedro Moritz de Carvalho Neto
* if the issues bound to the tracker should be displayed on the [[RedmineRoadmap|roadmap]]
12 1 Pedro Moritz de Carvalho Neto
* -if the issues bound to the tracker should be displayed on the [[RedmineIssueChangelog|changelog]]-, merged into [[RedmineRoadmap|roadmap]] view
13 1 Pedro Moritz de Carvalho Neto
* a different workflow
14 1 Pedro Moritz de Carvalho Neto
15 1 Pedro Moritz de Carvalho Neto
When creating a new tracker, you'll need to define its Workflow (see below) in order to properly use it. (To save time doing that -  you can copy an existing tracker's workflow when creating a new one.  To do that, select a tracker in the 'Copy workflow from' drop-down list on the 'New tracker' screen).
16 1 Pedro Moritz de Carvalho Neto
17 1 Pedro Moritz de Carvalho Neto
h2. Issue statuses
18 1 Pedro Moritz de Carvalho Neto
19 1 Pedro Moritz de Carvalho Neto
Issue statuses can be added and deleted freely. Each status has the following two configurable options:
20 1 Pedro Moritz de Carvalho Neto
* *Closed*: indicates that the issue is considered as closed (more than one status can be declared as closed)
21 1 Pedro Moritz de Carvalho Neto
* *Default*: status applied by default to new issues (only one status can be declared as default status)
22 1 Pedro Moritz de Carvalho Neto
23 1 Pedro Moritz de Carvalho Neto
h3. '% Done' and 'Done Ratio 'command
24 1 Pedro Moritz de Carvalho Neto
25 1 Pedro Moritz de Carvalho Neto
If you want to measure progress of work done, including % progress of work on Issues unfinished but partially done:
26 1 Pedro Moritz de Carvalho Neto
Then set the   [[RedmineSettings#Calculate-the-issue-done-ratio|"Calculate the issue done ratio" option]] in the application settings to "Use the issue status", which allows:
27 1 Pedro Moritz de Carvalho Neto
28 1 Pedro Moritz de Carvalho Neto
* As per screenshot below, you can set the % Done for each status - (if left blank, changing an issue to this status will not change its percent done.)
29 1 Pedro Moritz de Carvalho Neto
30 1 Pedro Moritz de Carvalho Neto
* After setting new values: use the 'Update Issue done ratios' command to set the " Done %" for all issues to match the values in the table:
31 1 Pedro Moritz de Carvalho Neto
32 1 Pedro Moritz de Carvalho Neto
!issue-done-ratio.png!
33 1 Pedro Moritz de Carvalho Neto
34 1 Pedro Moritz de Carvalho Neto
h2. Workflow
35 1 Pedro Moritz de Carvalho Neto
36 1 Pedro Moritz de Carvalho Neto
The workflow lets you define status transitions that the various project members are allowed to make on the issues according to their type.
37 1 Pedro Moritz de Carvalho Neto
38 1 Pedro Moritz de Carvalho Neto
On the workflow setup screen, select the role and the tracker for which you want to edit the workflow, then click 'Edit'. The screen lets you select the authorized transitions for the chosen role and tracker. The "Current status" column indicates the initial status of an issue. The "New statuses allowed" columns stand for the statuses that can be applied.
39 1 Pedro Moritz de Carvalho Neto
40 1 Pedro Moritz de Carvalho Neto
Note: For a user to change an issue status, they need to have either 'Edit' or 'Add note' permission (see [[RedmineRoles|Roles and permissions]]).
41 1 Pedro Moritz de Carvalho Neto
42 1 Pedro Moritz de Carvalho Neto
!workflow_example.png!
43 1 Pedro Moritz de Carvalho Neto
44 1 Pedro Moritz de Carvalho Neto
In the above example, Bugs with a New status could be given an Assigned or Resolved status by the Developer role. Those with an Assigned status could get a Resolved status. The status of all the other Bugs cannot be modified by the Developer.