Ability to customize column results in a filter/query

[aroach@…]

Much like when you create a SELECT statement, and you can choose what columns would like to return in the query — regardless of the constraints for the query — I'd like to request the ability to select what columns are displayed in a filter.

For example:

SELECT id, summary, component FROM ticket WHERE milestone = 'testmilestone';

Would display id, summary, and component in the recordset.

Now, if I tried this in the filter view, by including "component" I'm introducing another query constraint. In order to have all of the results to display "component", I have to keep adding components until I reach the end. There's no way for me to wildcard (that I'm aware of) because component is a selectbox.

Many thanks.

[Russell Hind <rhind@…>]

Not sure if this should be a separate query or not, but we are effectively serving multiple projects from 1 svn repo and 1 trac database. Hence we have components such as:

Project1/Area1 Project1/Area2 Project2/Area1

I'm not up on SQL and like the simple filter interface, but would like to be able to enter freeform text and wildcards for values such as component so rather than having to add multiple component lines to the filer (which may not be updated when new areas are added), I'd like to be able to enter

Project1/*

Cheers

Russell

[David Adler]

I second the request. I could imagine a user interface with a series of checkboxes for the user to specify which columns he wants to see in the results.

Related and also useful would be a way to specify globally what custom fields should appear by default in custom queries (and perhaps also in standard reports).

[JoshuaFranklin]

I would also like to customize column results.

In our project we have different people working on different components, but the components interact. Therefore we have a saved query on our front page that includes several (grouped) components so the different groups can see what's happening with the other group. Showing the component in the results would make this more clear.

[Christian Boos]

That's an often requested feature, we should implement this one day.

[anonymous]

As a mitigation, you can make all columns display by using the following patch:

trac/ticket/query.py

@@ -137 +137 @@
 
         # Only display the first eight columns by default
         # FIXME: Make this configurable on a per-user and/or per-query basis
-        self.cols = cols[:7]
-        if not self.order in self.cols and not self.order == self.group:
+        #self.cols = cols[:7]
+        self.cols = cols
+        #if not self.order in self.cols and not self.order == self.group:
             # Make sure the column we order by is visible, if it isn't also
             # the column we group by
-            self.cols[-1] = self.order
+            #self.cols[-1] = self.order
 
         return self.cols

[alexandra]

I second this request. I even tried the same underscore tricks that work for custom formatting for SQL custom reports, of course with no avail. So even just adding this to query language without any UI would be useful.

[eoin.dunne@…]

This feature would be awsome. You could basically do away with the custom reports capability if you could specify which columns to display.

I'm bumping the priority on this issue.

[Christian Boos]

Replying to alexandra:

I second this request. I even tried the same underscore tricks that work for custom formatting for SQL custom reports, of course with no avail. So even just adding this to query language without any UI would be useful.

Yes, that would be a first step. Related to #1735.

[writetodan@…]

Nice one, i third it.

Trac does seem pretty crippled without the user able to query all info, e.g. if user wants to see the latest updates, but can't sort by update time, since column not visible.

[writetodan@…]

(Okay latest updates is a bad example - i just found the timeline!)

[Christian Boos]

r4784 implements the possibility to specify the columns using the new col parameter in the TracQuery language.

What's left to be done is an UI for selecting them in the query view itself.

[alexandre.franke@…]

Replying to cboos:

What's left to be done is an UI for selecting them in the query view itself.

What's more Roadmap uses TracQuery to show open/closed tickets for a milestone. This should also be customizable.

[Christian Boos]

Replying to alexandre.franke@gmail.com:

What's more Roadmap uses TracQuery to show open/closed tickets for a milestone. This should also be customizable.

That could be useful for specifying the columns one would like to display. This could perhaps be done with a "[milestone] base_query = ?...<query href>..." setting?

[anonymous]

Replying to cboos:

That could be useful for specifying the columns one would like to display.

Exactly.

This could perhaps be done with a "[milestone] base_query = ?...<query href>..." setting?

Where would you change this setting from?

[Christian Boos]

Replying to anonymous:

Replying to cboos:

This could perhaps be done with a "[milestone] base_query = ?...<query href>..." setting?

Where would you change this setting from?

A normal TracIni setting in the [milestone] section?

[alexandre.franke@…]

Replying to cboos:

This could perhaps be done with a "[milestone] base_query = ?...<query href>..." setting?

Replying to alexandre.franke@gmail.com:

Where would you change this setting from?

Replying to cboos:

A normal TracIni setting in the [milestone] section?

Okay, seems nice.

[Eli Carter]

I've thrown together a rough implementation in sandbox/ticket-2821 to get this rolling again. Feedback welcome.

[anonymous]

Changes merged to trunk. If further enhancements are desired, please open a new ticket.

[dharris <dharris+trac@…>]

For reference, this merge was in changeset:5413