RedmineTimelogDetails » History » Version 8
Lucile Quirion, 2015-02-23 03:44
Describe the browsing path to timelog details
| 1 | 5 | Mischa The Evil | h1. Redmine Timelog Details |
|---|---|---|---|
| 2 | 1 | James Rowe | |
| 3 | 4 | Mischa The Evil | {{>toc}} |
| 4 | 1 | James Rowe | |
| 5 | h2. Introduction |
||
| 6 | |||
| 7 | After building a set of time entries through Redmine the *Timelog Details* page can help show running totals of time against a project. |
||
| 8 | |||
| 9 | 8 | Lucile Quirion | The *Timelog Details* page is accessible from the Overview > Spent Time > Details menu. |
| 10 | Note that the timelog feature is available only when the project's "Time tracking" module is activated. |
||
| 11 | |||
| 12 | 1 | James Rowe | h2. Searching |
| 13 | |||
| 14 | Shares the same search interface as [[RedmineTimelogReport]] |
||
| 15 | |||
| 16 | !SearchTimelog.png! |
||
| 17 | |||
| 18 | 3 | James Rowe | h2. Results |
| 19 | 1 | James Rowe | |
| 20 | By default the detail time log shows *all time* entries in the system. |
||
| 21 | |||
| 22 | From top to bottom in the image |
||
| 23 | * Total time result of the search |
||
| 24 | * pagination table of time entries |
||
| 25 | ** sortable columns |
||
| 26 | * Atom and CSV format available |
||
| 27 | |||
| 28 | Notice the bottom line has no issue, it was logged against the project. |
||
| 29 | |||
| 30 | 2 | James Rowe | Links work the same as the rest of the wiki; closed issues have strike through applied to them. |
| 31 | 1 | James Rowe | |
| 32 | 3 | James Rowe | h3. HTML output |
| 33 | |||
| 34 | 1 | James Rowe | !TimeLogDetails.png! |
| 35 | 3 | James Rowe | |
| 36 | h3. CSV output |
||
| 37 | 1 | James Rowe | |
| 38 | 2 | James Rowe | A sample CSV output of the above time entries (and attached): |
| 39 | 1 | James Rowe | |
| 40 | |_. Date |_. User |_. Activity |_. Project |_. Issue |_. Tracker |_. Subject |_. Hours |_. Comment | |
||
| 41 | |09/24/2010|Test Developer|Testing|Developers|10|Bug|Bug Report from Test user|0.333333|make sure the changes work| |
||
| 42 | |09/23/2010|Test Developer|Development|Developers|10|Bug|Bug Report from Test user|1.0|Doing the actual coding| |
||
| 43 | |09/23/2010|Test Developer|Implementation|Developers|11|Feature|Build a bridge|2.0|showing a closed issue| |
||
| 44 | |09/22/2010|Test Developer|Research|Developers|10|Bug|Bug Report from Test user|0.333333|what are the problems with this bug| |
||
| 45 | |09/22/2010|Test Developer|Design|Developers|10|Bug|Bug Report from Test user|1.0|Designing an elegant solution| |
||
| 46 | 2 | James Rowe | |09/21/2010|Test Developer|Support|Developers| | | |1.0|Create this project and demo issue| |