RedmineIssueTrackingSetup » History » Version 37

Bernhard Rohloff, 2019-03-08 16:36
Added content for fields permissions section

1 1 Jean-Philippe Lang
h1. Issue tracking system
3 33 Go MAEDA
4 9 Mischa The Evil
5 5 Jean-Philippe Lang
h2. Trackers
7 18 dj jones
Trackers are how you split your issues into different types - common ones are Bug, Feature, Defect or etc.
9 33 Go MAEDA
For each tracker, you can define: (see image below)
10 28 dj jones
* Name  (the example pictured is 'Bug')
11 36 Go MAEDA
* Default status (an issue status applied by default to new issues)
12 34 Go MAEDA
* If the issues bound to the tracker should be displayed on the [[RedmineRoadmap|roadmap]]
* A different workflow
* Standard and custom fields available for the tracker
15 1 Jean-Philippe Lang
16 35 Go MAEDA
!{width: 776px;}.tracker_config@2x.png!
17 33 Go MAEDA
18 25 dj jones
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).
19 5 Jean-Philippe Lang
20 1 Jean-Philippe Lang
h2. Issue statuses
22 36 Go MAEDA
Issue statuses can be added and deleted freely. Each status has the following configurable option:
* *Issue closed*: indicates that the issue is considered as closed (more than one status can be declared as closed)
25 4 Jean-Philippe Lang
26 33 Go MAEDA
h3. '% Done' and 'Done Ratio' command
27 1 Jean-Philippe Lang
28 24 dj jones
If you want to measure progress of work done, including % progress of work on Issues unfinished but partially done:
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:
30 19 dj jones
31 22 dj jones
* 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.)
32 12 Tharuka Pathirana
33 30 dj jones
* 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:
34 12 Tharuka Pathirana
35 32 Go MAEDA
!{width: 776px;}.issue-done-ratio@2x.png!
36 1 Jean-Philippe Lang
h2. Workflow
38 12 Tharuka Pathirana
39 33 Go MAEDA
h3. Status transitions
41 16 Youssef Eldakar
The workflow lets you define status transitions that the various project members are allowed to make on the issues according to their type.
42 1 Jean-Philippe Lang
43 16 Youssef Eldakar
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.
44 1 Jean-Philippe Lang
45 31 Toshi MARUYAMA
Note: For a user to change an issue status, they need to have either 'Edit issues' permission (see [[RedmineRoles|Roles and permissions]]).
46 1 Jean-Philippe Lang
!{width: 776px}.workflow_example@2x.png!
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.
50 33 Go MAEDA
h3. Fields permissions
53 37 Bernhard Rohloff
On this tab one can set special permissions to a field in a specific state. One can choose between the attributes @read-only@, @required@, or leave it empty for default behavior. If the field is set as @read-only@ it is hidden in the edit section and can not be changed by the selected role. If the field is set to @required@ it can not be left empty when the issue gets edited by the selected role.
{{thumbnail(workflow_fields_permissions.png, size=350, title='Field permissions section')}}