seems to ignore time data from timingandestimationplugin 1.2.7

[anonymous]

I'm stuck with this issue, see attachment: duration, start/end times are always 2days, current day despite correct data entered for the timingandestimationplugin 1.2.7 plugin. Would be a blocker for me

[Chris Nelson]

Can you post the TracPM and Trac-jsGantt sections of your trac.ini?

[anonymous]

tracjsgantt.tracjsgantt.tracjsganttchart = enabled
tracjsgantt.tracjsgantt.tracjsganttsupport = enabled
tracjsgantt.tracpm.projectsorter = enabled
tracjsgantt.tracpm.resourcescheduler = enabled
tracjsgantt.tracpm.simplecalendar = enabled
tracjsgantt.tracpm.simplesorter = enabled
tracjsgantt.tracpm.tracpm = enabled

[Chris Nelson]

Replying to anonymous:

tracjsgantt.tracjsgantt.tracjsganttchart = enabled
tracjsgantt.tracjsgantt.tracjsganttsupport = enabled
tracjsgantt.tracpm.projectsorter = enabled
tracjsgantt.tracpm.resourcescheduler = enabled
tracjsgantt.tracpm.simplecalendar = enabled
tracjsgantt.tracpm.simplesorter = enabled
tracjsgantt.tracpm.tracpm = enabled

You need to configure fields to link to T&E. See step 3 of installation instructions.

[anonymous]

ohhh-k, got it. now I get a number of 'userstart is not a custom ticket field' errors but guess I have to lookup the right fields names from the other plugins

[anonymous]

Replying to anonymous:

ohhh-k, got it. now I get a number of 'userstart is not a custom ticket field' errors but guess I have to lookup the right fields names from the other plugins

tried to lookup in the docs but there seems to be no clue regarding such field names to use. basically I'm stuck with 0-length bars. Any clue?

[Chris Nelson]

Replying to anonymous:

Replying to anonymous:

ohhh-k, got it. now I get a number of 'userstart is not a custom ticket field' errors but guess I have to lookup the right fields names from the other plugins

tried to lookup in the docs but there seems to be no clue regarding such field names to use. basically I'm stuck with 0-length bars. Any clue?

If you aren't already using custom fields for start and/or finish, remove their configuration from the Gantt. Remove lines that look like:

## Ticket field to use as the data source for start date (default: None)
fields.start = userstart
## Ticket field to use as the data source for finish date (default: None)
fields.finish = userfinish

If you want to be able to specify start and/or finish dates, you need to create custom fields with something like:

userfinish = text
userfinish.date = true
userfinish.date_empty = true
userfinish.label = Due Date
userfinish.order = 17

in the [ticket-custom] section of trac.ini

[anonymous]

ok. tried, but then I get

ambiguous column name: userstart.value

[Chris Nelson]

Replying to anonymous:

ok. tried, but then I get

ambiguous column name: userstart.value

I don't know. What does the Trac log say?

[anonymous]

2012-05-15 15:41:35,784 Trac[formatter] ERROR: Macro TracJSGanttChart(milestone=1.2.4, dateDisplay=dd/mm/yy, openLevel=2, status=new|accepted|assigned|reopened) failed:
Traceback (most recent call last):
  File "build/bdist.linux-i686/egg/trac/wiki/formatter.py", line 717, in _macro_formatter
  File "build/bdist.linux-i686/egg/trac/wiki/formatter.py", line 304, in process
    def __init__(self): pass
  File "build/bdist.linux-i686/egg/trac/wiki/formatter.py", line 291, in _macro_processor
    def assert_line_data(self, flag=1):
  File "build/bdist.linux-i686/egg/tracjsgantt/tracjsgantt.py", line 659, in expand_macro
  File "build/bdist.linux-i686/egg/tracjsgantt/tracjsgantt.py", line 554, in _add_tasks
  File "build/bdist.linux-i686/egg/tracjsgantt/tracjsgantt.py", line 305, in _query_tickets
  File "build/bdist.linux-i686/egg/trac/ticket/query.py", line 298, in execute
  File "build/bdist.linux-i686/egg/trac/ticket/query.py", line 279, in _count
  File "build/bdist.linux-i686/egg/trac/db/util.py", line 65, in execute
  File "build/bdist.linux-i686/egg/trac/db/sqlite_backend.py", line 78, in execute
  File "build/bdist.linux-i686/egg/trac/db/sqlite_backend.py", line 56, in execute
  File "build/bdist.linux-i686/egg/trac/db/sqlite_backend.py", line 48, in _rollback_on_error
OperationalError: ambiguous column name: userstart.value

[Chris Nelson]

I suspect you userstart and userfinish fields are misconfigured somehow. Did you add them from admin or did you manually edit trac.ini? I encourage the former. But, again, if you aren't yet using them, just remove their configuration from TracPM and/or Trac-jsGantt.

[anonymous]

I see ... I edited the .ini, but the TRAC docs say text type custom tickets can have options .value, .label, .order, .format, not .date or .date_empty as in your e.g.; also, it says the DB must be updated manually, but the sample SQL code given for sqlite doesn't work. I see no UI into Admin to do this stuff user-friendly, so seems the only possibility is doing by hand (with the right sintax)

[anonymous]

ok, done via shell sqlite3; and 'ambiguous column' error seems was due to a dirty char not visible in vi :/ now I have

userstart = text
userstart.value =
userstart.label = Start Date
userstart.order = 17
userstart.format = plain
userfinish = text
userfinish.value =
userfinish.label = Due Date
userfinish.order = 18
userfinish.format = plain