Support

It accumulates.

In your example, the total time recorded for the ticket will be 35 minutes.

You can't see the time per ticket, you can only see the time each manager has spent per month, and the total time spent per client.

If you want to display the time per ticket you'd have to do a template override to show the timespent value of the ticket object. That's where the accumulated time is recorded.

If you want to display the time per post you'd have to do a different template override to show the timespent value of the post object.

If either of these are interesting to you, or if you want to display this information elsewhere, please let me know. I can't build a feature for a use case I neither know about nor have myself. Give me the use case and I can figure out some code.

In this case, the information you need is already shown to category managers when viewing a ticket. See the attachment for a screenshot (I have not recorded any time on your ticket which is why you see 0.00 in the screenshot).

If you meant something different, please let me know.

Perfectly clear now.

I am making the following changes:

• Added a column in the backend Tickets page with the time spent per ticket, displayed as Hours:minutes:seconds.
• Employ Joomla's feature to show/hide table columns so you can hide any of the columns in the backend tables you don't need.
• If you are a support category manager you will now be able to see the time spent per post in the post's header, to the right of the date and time.

This will give you good visibility into how time was spent for each ticket.

If you have any comments, ideas, or objections please do let me know.

I expect to be able to make a new release towards the end of September.

The only reason I am noncommittal is that Joomla! 5.2 is coming in mid October. Assuming that there are no b/c breaks which are not mentioned in its Migrations documentation I will have no problem making a release in 3-4 weeks. If we see any last minute changes which break something we might have to push the release back a bit to apply any necessary changes. That said, the releases from 4.2 onwards have been fairly well behaved in terms of last minute breaking changes (namely, the lack thereof), so we have high hopes for this release as well!