Modify ↓
Opened 13 years ago
Closed 13 years ago
#9534 closed defect (duplicate)
Overriding explicit start dates
Reported by: | Robert Inder | Owned by: | Chris Nelson |
---|---|---|---|
Priority: | high | Component: | TracJsGanttPlugin |
Severity: | critical | Keywords: | |
Cc: | Trac Release: | 0.12 |
Description
The trac-hacks description page says...
When estimate and finish are both configured (and start is not configured or not on the ticket), the plugin attempts to determine the start of the task from finish and estimate as start = finish - estimate with consideration for weekends and hours per day.
But actually, the start date is ignored.
My trac.ini contains...
[trac-jsgantt] # To work with Timing and Estimation for percent complete fields.estimate = estimatedhours fields.worked = totalhours # Each unit in estimate is 1/8 of a day days_per_estimate = 0.125 # To work with Master Tickets for dependencies fields.pred = blockedby fields.succ = blocking # To work with Subtickets for parent/child relationships fields.parent = parents # # To work with ChildTickets plugin # parent_format = #%s # # Custom fields for start and due dates fields.start = userstart fields.finish = userfinish # date_format = %Y-%m-%d # date_format = %d/%m/%Y milestone_type = milestone
and
userstart = text userstart.label = Start Date userstart.order = 4 userstart.value = userstart.date = true userstart.date_empty = true userfinish = text userfinish.label = Finish Date userfinish.order = 4 userfinish.value = userfinish.date = true userfinish.date_empty = true
But the gantt charts always calculate their own start dates and ignore the ones in userstart.
Attachments (0)
Change History (2)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I think this is a duplicate ticket of #9279