1 Dec 2008 17:42
[Trac-dev] Re: Semi-intelligent column removal in ticket query
Erik Bray <hyugaricdeau <at> gmail.com>
2008-12-01 16:42:03 GMT
2008-12-01 16:42:03 GMT
On Sat, Nov 29, 2008 at 4:18 AM, Remy Blank <remy.blank <at> pobox.com> wrote: > Erik Bray wrote: >> +1 here. I've already removed it in my own Trac instances for the >> reasons you've described. At one point I spent some time trying to >> make this a little more dynamic so that columns would be re-added if >> the grouping column was changed, but then you had to keep track of >> whether or not that column was enabled or disabled to begin with, and >> it just becomes too cumbersome. > > I came to the same conclusion. > > It's not the first time that you mention having removed or changed > something in your installations and that has been requested later > independently. Any other good ideas that I could implement? I'm good at > cleaning up(Continue reading)Not really at the moment, though there is a patch I'm about to go work on concerning default values for enum fields. But I'll attach that to a ticket when it's done. >> Easier to just remove the restriction and allow users to add a column >> even if the results are already grouped by that column. Some of my >> users actually wanted to be able to do that so that they could include >> a column when doing a CSV export, but still view the results grouped >> by that column. > > I have implemented something slightly different: I have removed the > algorithm from get_all_columns(), which is used to create the list of > check boxes, so all checkboxes are always present. And I have moved it
Not really at the moment, though there is a patch I'm about to go work
on concerning default values for enum fields. But I'll attach that to
a ticket when it's done.
>> Easier to just remove the restriction and allow users to add a column
>> even if the results are already grouped by that column. Some of my
>> users actually wanted to be able to do that so that they could include
>> a column when doing a CSV export, but still view the results grouped
>> by that column.
>
> I have implemented something slightly different: I have removed the
> algorithm from get_all_columns(), which is used to create the list of
> check boxes, so all checkboxes are always present. And I have moved it
RSS Feed