Clicking the 'Update' button on a custom ticket query changes grouping/sort criteria

[aburke@…]

It seems as though clicking the 'Update' button on a custom TracQuery does not persist all the values as one would expect. For example, in a query with "owner=$USER", it seems as though the 'owner' dropdown is not being populated.

I am running TracAccountManager (0.2.1dev-r4679) which could potentially be having an effect.

[osimons]

Could you update the "Version" field to your Trac version? It is required when trying to make sense of bug reports. Also, you may want to look at #1467 (at the bottom) and #7258 - are either a duplicate of the issue you experience? Do you have restrict_owner enabled?

Please report back.

[aburke@…]

Apparently I need to write some more text here in an attempt to get past the spam filters.

[anonymous]

I do have 'restrict_owner' set to true, but the query works at first. It's just if you change filter settings and click 'Update' that the owner field is lost. It does not appear to be a duplicate of those other issues, at least based on my reading of them.

[osimons]

Tested it again, and it is a duplicate of #7258 as it cannot store the value $USER anywhere seeing the dropdown is populated with usernames only. When you first hit the query it works, but any subsequent update will have empty owner. Turning off restrict_owner makes it behave like a text field - and updates works.