| 17 | | * Compared to TracJsGanttPlugin, this plugin does not compute the completed percents from custom ticket fields like 'remaininghours' or 'estimatedhours' but you set the completion value in the range of 0 to 100% in the ticket form, manually. |
| 18 | | * The meaning of start and end date of a ticket displayed in the chart is at the discretion of you. Usually, you set the planned time period, though you cannot see in the gantt chart if completion had started earlier than planned, was interrupted or has finished later. For a review of the work history, you may interpret start and end date to indicate the worked time period. This is up to you. |
| | 17 | |
| | 18 | * The Start/End date of a ticket are defined as follows. |
| | 19 | |
| | 20 | `Start Date`: the date that a task actually began |
| | 21 | |
| | 22 | `End Date`: the date that a task is scheduled to be completed |
| | 23 | |
| | 24 | but you may interpret the meaning of the date differently. It is up to you (or your team) to define them. |
| | 25 | |
| | 26 | * This plugin is designed to use with the time tracking plugin: TimingAndEstimationPlugin, TracHoursPlugin |
| | 27 | |
| | 28 | and it is designed to ignore the `Completed Percents` of a closed ticket. |
| | 29 | |
| | 30 | In case of a closed ticket, `Total Hours` is used instead of `Completed Percents`. |
| | 31 | |
| | 32 | And '''it is strongly recommended to use with the time tracking plugin'''. |
| | 33 | |
| | 34 | Compared to TracJsGanttPlugin, this plugin does not compute the `Completed Percents` from custom ticket fields like 'remaininghours' or 'estimatedhours', |
| | 35 | |
| | 36 | but you set the completion value in the range of 0 to 100% in the ticket form, manually. |
