Add support for date calculations in ticket reports/querys

[anonymous]

This enables rudimentary project management

[Christopher Lenz]

Please be more specific. What kind of calculations do you have in mind?

[anonymous]

Date calculations for reports might include the following:

• All tickets with field1 before or after a given date
• All tickets with field1 before/after field2 by a certain amount (in the same ticket)
• All tickets with field1 before or after field2 from a particular ticket

Examples questions that could be answered through such reports:

• Which tickets are not expected to be completed by a certain date?
• Which tickets are expected to be completed more than a week after their targets?
• Which tickets are expected to start before this ticket is expected to complete?

This assumes that a custom field has been defined for start, targeted, and expected dates.

[Emmanuel Blot]

I think you can do this kind of requests with custom SQL requests, can't you ?

[anonymous]

It would be pretty tough if the data isn't stored as a date. The custom request would have to validate the entry as a data/put it in canonical form & then do the computation.

It strikes me a very difficult to pull off without #1942, and your comment there suggests that #1942 may be a serious piece of work.

[Christian Boos]

#4594 was closed as duplicate.

See also #2288 which is more about adding time query capabilities to the custom query UI.

[Peter Suter]

Replying to anonymous:

Date calculations for reports might include the following:

• All tickets with field1 before or after a given date

Examples questions that could be answered through such reports:

• Which tickets are not expected to be completed by a certain date?

This assumes that a custom field has been defined for start, targeted, and expected dates.

That part should be possible now with e.g. [[TicketQuery(expected_completion_date=in1month..)]] assuming a custom ticket

[ticket-custom]
expected_completion_date = time
expected_completion_date.format = relative