id summary reporter owner description type status priority component severity resolution keywords cc release 11074 Clean/New Project tries to use mastertickets table Matthias Andreas "Hi anbo, ich halte es mal Englisch für den Report. :) -- Reproduce as follows: * Create a new project with ProjectPlanPlugin. * Provoke usage of the mastertickets/legacy check * it should suffice to load the plugin's configuration or use a macro since ppenv invokes the check (and ppenv is used by the most - if not all - sub-components) * Create a new ticket * Use a Macro (which gets at least one Ticket) Result: As an example: report/gvhierarchical lines from the Examples. {{{ Error: Macro ProjectPlan(macroid=report_buffer,renderer=report_buffer,limitlines=4) failed no such table: mastertickets .. Error: Macro ProjectPlan(macroid=1,renderer=gvhierarchical) failed no such table: mastertickets }}} Masterticket compatibility is enabled. {{{ exile ppptesting # cat conf/trac.ini | grep master enable_mastertickets_compatiblity_mode = enabled }}} Checking the db (sqlite3) shows the legacy mode should be used. {{{ sqlite> SELECT * FROM ticket; 1|task|1368416929241503|1368416972380224|component1||critical|admin|admin||||closed|duplicate|Invent the Wheel|Should be round| sqlite> SELECT * FROM ticket_custom; 1|dependencies| 1|due_assign|01.01.2000 1|due_close|01.02.2000 sqlite> SELECT * FROM mastertickets; Error: no such table: mastertickets }}} -- If the Mastertickets Plugin (or its Table) should be used, it may be better to enforce (and check) the use of Mastertickets since it hooks itself in the Ticketsystem. (didn't test it but i guess it is possible to check if the plugin is enabled in the configuration section ""components"") Greetings, makadev" defect closed low ProjectPlanPlugin normal worksforme 1.0