RedmineIssues » History » Version 13
Brice P, 2010-04-23 08:58
1 | 1 | Thomas Lecavelier | h1. Issue Tracking |
---|---|---|---|
2 | 1 | Thomas Lecavelier | |
3 | 3 | Mischa The Evil | Issues are the heart of the Redmine business. An issue is bound to a project, owned by a user, can be related to a version, etc. |
4 | 1 | Thomas Lecavelier | |
5 | 7 | Tom Rochette | h2. Listing of the issue |
6 | 7 | Tom Rochette | |
7 | 7 | Tom Rochette | From a selected issue page, you can see the work in progress that is done to fix the issue. The messages are displayed in chroonological order, starting from the oldest to the newest message. It is possible to quote others' messages as well as to edit yours. |
8 | 7 | Tom Rochette | |
9 | 9 | Tom Rochette | h3. Related issues |
10 | 9 | Tom Rochette | |
11 | 9 | Tom Rochette | Related issues allow developers to link issues to each other in order to remove duplicates or simplify their workflow. |
12 | 9 | Tom Rochette | |
13 | 9 | Tom Rochette | It is possible to link issues based on various relations. Current relations are: |
14 | 9 | Tom Rochette | * related to |
15 | 9 | Tom Rochette | * duplicates |
16 | 11 | Brice P | If issue B is the duplicate of A |
17 | 11 | Brice P | - closing B will let A open |
18 | 11 | Brice P | - closing A will close B |
19 | 9 | Tom Rochette | * blocks |
20 | 12 | Brice P | If issue B blocks A, |
21 | 12 | Brice P | A can't be closed unless B is. |
22 | 9 | Tom Rochette | * precedes |
23 | 13 | Brice P | If B follows A, you can't give B |
24 | 13 | Brice P | a starting date equal or less |
25 | 13 | Brice P | than the ending date of A. |
26 | 1 | Thomas Lecavelier | * follows |
27 | 12 | Brice P | If issue B follows A (ex A ends the 21/04 and B begins the 22/04) |
28 | 11 | Brice P | and you add +2 day at the ending date of A, |
29 | 11 | Brice P | the starting and ending dates of B will be +2 too. |
30 | 9 | Tom Rochette | |
31 | 9 | Tom Rochette | !redmine-related-issues.png! |
32 | 9 | Tom Rochette | |
33 | 10 | Tom Rochette | Administrators can define the [[RedmineRoles#Permissions|permissions]] of users to add and edit such relations. |
34 | 10 | Tom Rochette | |
35 | 9 | Tom Rochette | h3. Watchers |
36 | 9 | Tom Rochette | |
37 | 9 | Tom Rochette | Display a list of all the users who are watching this issue. If the issue is updated, those users will be notified. |
38 | 9 | Tom Rochette | |
39 | 9 | Tom Rochette | If you are logged in as a project administrator, it is possible for you to add users to the watch list on this page. By clicking on the Add link, a drop-down menu with a *Add* button appear, which allows you to select which user to add to the watch list. |
40 | 9 | Tom Rochette | |
41 | 9 | Tom Rochette | !redmine-watchers.png! |
42 | 10 | Tom Rochette | |
43 | 10 | Tom Rochette | Administrators can define the [[RedmineRoles#Permissions|permissions]] of users to add/delete watchers as well as to see the list of watchers. |
44 | 9 | Tom Rochette | |
45 | 7 | Tom Rochette | h3. Associated revisions |
46 | 7 | Tom Rochette | |
47 | 8 | Tom Rochette | If the administrator has defined [[RedmineSettings#Referencing-issues-in-commit-messages|Referencing Issues Keywords]], a developer that uses such keyword(s) will see its commit message displayed on the issue page, under the Associated revisions block (generally to the right of the first reply). |
48 | 7 | Tom Rochette | |
49 | 7 | Tom Rochette | !redmine-associated-revision.png! |
50 | 7 | Tom Rochette | |
51 | 1 | Thomas Lecavelier | h2. Adding a new issue |
52 | 1 | Thomas Lecavelier | |
53 | 6 | Tom Rochette | People can create a new issue when they meet the [[RedmineRoles|roles and permissions]] configured by the Redmine Administrator ([[RedmineRoles#Permissions|Role: Issue Tracking > Add Issues]]). |
54 | 4 | Mischa The Evil | When creating a new issue, one of the most important items is the [[RedmineIssueTrackingSetup#Trackers|tracker field]], which defines the nature of the issue. By default, Redmine comes with three different trackers: _bug_, _feature_, and _support_. |
55 | 1 | Thomas Lecavelier | |
56 | 1 | Thomas Lecavelier | h2. Updating an existing issue |
57 | 1 | Thomas Lecavelier | |
58 | 1 | Thomas Lecavelier | (TODO: describe and upload a screen-shot of update panel) |
59 | 1 | Thomas Lecavelier | |
60 | 5 | Anthony Cartmell | h2. Editing an existing issue's Subject or Description |
61 | 1 | Thomas Lecavelier | |
62 | 6 | Tom Rochette | In order to edit an existing issue, your role has to have the [[RedmineRoles#Permissions|Issue Tracking > Edit Issues]] right. This right gives you a _(More)_ link after the Change Properties section title in the "Update issue" panel. |
63 | 5 | Anthony Cartmell | |
64 | 5 | Anthony Cartmell | Clicking on the _(More)_ link will bring-up an editable copy of the Subject and Description of the issue. |
65 | 2 | Thomas Lecavelier | |
66 | 2 | Thomas Lecavelier | p=. !RedmineEditIssue_More_Link.png! |