[PATCH] Add support for configuring a default set of columns to show in a query.
|Reported by:||Torbjörn Svensson <azoff@…>||Owned by:|
At my work, we are using trac to view our bugs and tasks, but one of our customer uses JIRA, so we export our issues from JIRA and import them in trac as a tickets. To keep track of the issues, we have a custom field called 'jira' that contains the upstream id. As the upstream id is quite important, we want to include the column in the set of default columns for a query. The attached patch introduces two new config directives, one for setting the default order in the query (rather than hardcoding it to be 'priority', still a fallback through…), the second is a list of columns to automatically show unless the user specified a set of columns.
Examples: Using this link results in the following set of columns shown in the browser (verified here on t.e.o):
With my patched applied and the following in the trac.ini
[query] default_cols = id,time,changetime,priority
would result in the following columns shown in the browser:
Change History (27)
Changed 19 months ago by Torbjörn Svensson <azoff@…>
comment:4 in reply to: ↑ 2 ; follow-up: ↓ 5 Changed 19 months ago by rblank
- Milestone set to next-major-0.1X