ticket summary type release owner status created modified _description _reporter 12200 Add number of tickets in each column enhancement 0.12 jpsave new 2015-02-20T14:44:53+01:00 2015-02-20T14:44:53+01:00 As the amount of tickets present in columns may not fit the display page size, it could be interesting to set on top of each column a number of tickets shown. jpsave 12593 Filter whiteboard tickets with custom query instead of 'On Ticketsboard' field enhancement jpsave new 2015-11-27T18:40:37+01:00 2015-11-27T18:40:37+01:00 "= Current situation At the moment, the use of the virtual whiteboard asks for an update on each tickets so that it appears/disappears on the board. When a milestone is closed, and a new one is started, you may need to update a great number of tickets according to that. = Feature proposal * Remove 'On Ticketsboard' custom field and replace it by a custom query. It may be based on a report that is settled by a variable in trac.ini. For example: {{{#!ini [ticketsboard] inputreport = 4 }}} * Create a custom macro that would allow to build a whiteboard based on the tickets available in the request {{{ [[TicketsBoard([],[],[],[])]] }}} * {{{}}}: custom query to select tickets that are displayed on the board * {{{}}}: fields that are displayed on each ticket * {{{}}}: column of the board (default value would be status) * {{{}}}: values that should appear in column of the board (e.g. new, accepted, closed) A complete example for this macro would be: {{{ [[TicketsBoard(milestone=1.0,owner,estimated_time,status,new|accepted|closed)]] }}}" c.rabemananjara@… 13093 Restrictions are not checked defect jpsave new 2017-03-02T08:30:02+01:00 2017-03-02T08:30:02+01:00 "From comment:3:ticket:13069: On the line where the exception is generated, the status is used as a key for the `states_action` dict, however the keys of the dict are actions, not statuses: [browser:ticketsboardplugin/trunk/ticketsboardplugin/web_ui.py@16237:349#L348]." Ryan J Ollos