Recently updated is working on the modified_date field:

ORDER BY a.modified_date DESC

So we need one more filter option like recently commented?

How does it decide that it is modified if a comment is not a modification?
Is it just recording modified on edits to the first comment? If so then that is useless. Why would we want that?

Just explored the code - a comment does not alter modified_date field. It only adds info into the activities table. As far as I can see modified_date is altered only during the status changes.

@brianteeman do you think that a comments should update modified_date and modified_by fields? What do others think about it?

I feel like the issue and the issues comments are related, but not the
same. I also think that comments are activities, as are creating new issues
or editing issues. To me the proper thing to do would be to put everything
like new comments and updates to an issue all into the activities table,
and make that what we use for things like "recently updated". Perhaps
consider changing from recently updated to " recent activities". That
could include all the actions of comments, issue updates, and anything else
that happens.

On Friday, December 13, 2013, Dmitry Rekun wrote:

@brianteeman https://github.com/brianteeman do you think that a
comments should update modified_date and modified_by fields? What do
others think about it?

—
Reply to this email directly or view it on GitHub#273 (comment)
.

@drmmr763 for the issues I take the created date as related to the issue and modified date as related to the comments

@all for me ANY activity on the issue is an update (or modification)
You may blame the J!Tracker Application for transmitting this comment.

for me ANY activity on the issue is an update (or modification)

And from the speed perspective it's also a small win, because the query will be simple. Otherwise we should join over the activities table.

Thoughts on it?

I agree that a comment should be an update to an issue, and therefore be reflected in any "latest" filter for activity, update or modification.

It's just what I expect to see from such filters, there could even be an "include comments" or "exclude comments" checkbox if this would help clarify what is being filtered.

+1. Last modified should be the last time anything associated with an item
is modified IMO. Joomlacode updates the modified date with every save
action basically, we should too.

On Wed, Jan 15, 2014 at 12:53 PM, Chris Jones-Gill <notifications@github.com

wrote:

I agree that a comment should be an update to an issue, and therefore be
reflected in any "latest" filter for activity, update or modification.

It's just what I expect to see from such filters, there could even be an
"include comments" or "exclude comments" checkbox if this would help
clarify what is being filtered.

—
Reply to this email directly or view it on GitHub#273 (comment)
.

Ok, most are for the comments affecting modified_date. Will start to implement then

Testing it :)
You may blame the J!Tracker Application for transmitting this comment.