Enable use of 'time' and 'changetime' fields within the query module

[ilias@…]

e.g.: "order=time" and "order=changetime" do not work.

ordering based on "changetime" is important, in order to identify simply active/inactive tickets.

Most possibly, the fields will become available by adding them to this function:

source:trunk/trac/ticket/api.py#3935#L88​

testing order=changetime

keyword-parameter

[[TicketQuery(status=assigned|new|reopened, order=changetime, format=table )]]

[[TicketQuery(status=assigned|new|reopened&order=changetime, format=table )]]

context: ​http://dev.lazaridis.com/base/wiki/PlanTicketQueryMacro

[Christopher Lenz]

This is a duplicate of #2288.

[ilias@…]

This one is just about the core functionality (as used from trac-query macro), and does not affect the UI part.

see the following patch.

[ilias@…]

very basic patch which enables ordering on "time" and "changetime"

[ilias@…]

(supersedes previous patch) woks fine, but misses Timestamp formatting in textfields.

[ilias@…]

Timestamp fields are properly formatted within the UI

[ilias@…]

previous patch led to a crash. This one works with the UI query module, too.

[ilias@…]

to avoid confusion:

those 2 patches allow sorting on the two datetime fiels (time, changetime), whilst displaying the datetime values correctly:

attachment:TicketQueryMacroAddTimestampFields.diff​ attachment:TicketQueryMacroAddTimestampFormattingInt.diff​

It would be nice to have them applied to the trunk, before more changes are introduced during the upcoming rework of cboos.

[ilias@…]

In order to simplify this ticket:

I've moved the part which subjects a defect (ticket api) to #4019

The remaining enhancement patch for this ticket is this one:

attachment:TicketQueryMacroAddTimestampFormattingInt.diff​

It would be possibly more elegant to declare the fields 'time' and 'changetime' as "datetime" instead of "text", and to handle formatting within the templates.

[ilias@…]

superseded by #4174

other related tickets: #4158, #4019 and others

Ticket 'wontfix' in the way suggested, closing.

[ilias@…]

not wontfix, but superseded by refined tickets, thus this one become a duplicate of:

#4158, #4174