Edgewall Software
Modify

Ticket #3990 (closed enhancement: duplicate)

Opened 3 years ago

Last modified 5 weeks ago

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

Reported by: ilias@… Owned by: jonas
Priority: normal Milestone:
Component: ticket system Version: devel
Severity: normal Keywords:
Cc:

Description

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

Attachments

TicketQueryMacroTimeOrdering.diff Download (547 bytes) - added by ilias@… 3 years ago.
very basic patch which enables ordering on "time" and "changetime"
TicketQueryMacroAddTimestampFields.diff Download (666 bytes) - added by ilias@… 3 years ago.
(supersedes previous patch) woks fine, but misses Timestamp formatting in textfields.
TicketQueryMacroAddTimestampFormatting.diff Download (562 bytes) - added by ilias@… 3 years ago.
Timestamp fields are properly formatted within the UI
TicketQueryMacroAddTimestampFormattingInt.diff Download (1.3 KB) - added by ilias@… 3 years ago.
previous patch led to a crash. This one works with the UI query module, too.

Change History

comment:1 Changed 3 years ago by cmlenz

  • Status changed from new to closed
  • Resolution set to duplicate

This is a duplicate of #2288.

comment:2 Changed 3 years ago by ilias@…

  • Status changed from closed to reopened
  • Resolution duplicate deleted

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.

Changed 3 years ago by ilias@…

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

Changed 3 years ago by ilias@…

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

Changed 3 years ago by ilias@…

Timestamp fields are properly formatted within the UI

Changed 3 years ago by ilias@…

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

comment:3 Changed 3 years ago by 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 Download attachment:TicketQueryMacroAddTimestampFormattingInt.diff Download

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

comment:4 Changed 3 years ago by 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 Download

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.

comment:5 Changed 3 years ago by ilias@…

  • Status changed from reopened to closed
  • Resolution set to wontfix

superseded by #4174

other related tickets: #4158, #4019 and others

Ticket 'wontfix' in the way suggested, closing.

comment:6 Changed 3 years ago by ilias@…

  • Status changed from closed to reopened
  • Resolution wontfix deleted

comment:7 Changed 3 years ago by ilias@…

  • Status changed from reopened to closed
  • Resolution set to duplicate

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

#4158, #4174

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
to The owner will be changed from jonas. Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.