Redmine

This is a screenshot of the feature.

But it should be considered that processing when event variable is nil in the following code. It causes undefined method `[]' for nil:NilClass error at the next line.

  def last_activity(project)
    event = Redmine::Activity::Fetcher.new(User.current, :project => project).events(nil, nil, :limit => 1)[0]
    byebug
    event[:updated_on].nil? ? event[:created_on] : event[:updated_on]
  end

Go Maeda,

Thank you for your reply. I had already patched production (https://github.com/fredsdc/redmine/tree/3.2-patched), and I forgot I had posted the patch to Redmine.org. Fixed it again today to call last_activity function only once.

It now returns the project creation date if there is no activity in the project.

Thank you for updating the patch. It works fine, looks good to me.

Although Jean-Phillipe Lang wrote on #13696#note-7 as follows, last activity is very useful to maintenance projects.

We'll add this as an optional column when the project list will be made configurable (like the issue list).

In my opinion, "Last activity" is far more useful information than "Created".
Could this be a part of 3.4.0?

Go MAEDA wrote:

In my opinion, "Last activity" is far more useful information than "Created".

I'm not saying that this information is not usefull. It generates dozens of SQL queries and can make the project list really slow. We'll make this information available once the project list can be configured, but we can't add it by default now.

I have a new patch. I added a new option to the fetcher library, if set, the result is a hash { project_id -> last_activity }, that I use in the view.

Summarizing I reduced the queries to one per event type, which takes now a fraction of a second to complete.

I fixed a bug, and moved some code from the helpers to the controllers. I also had an idea how to always show some activity as Feature #3099.

It worked on Redmine trunk with the same changes. note-11

Attach a screen copy of my environment.
Last activity is not displayed for projects with 0 tickets.
However, as it can be seen from the Created column, I think that it is enough as it is.

Based on Frederico Camara work, I've created a patch that adds the "Last activity" column to the projects list.

Sorting by this column is not possible for now because I'm not sure how to implement it easily (the last activity date is calculated based on multiple tables). Any suggestion is welcome.

Slightly improved the patch in order to avoid some unnecessary joins when counting the number of results.

Updated the patch for current trunk.

• review the changes proposed by Frederico Camara to activity fetcher
• check for any solution to enable projects sorting by last activity date

Updated the patch to apply cleanly on the current trunk.

The last activity date is now available as a column in Project query, I just committed the patch.

Frederico Camara, did you find a way to make the column sortable? or should I take a look into this?

I'm closing this without the option to sort by Last activity date, we will track this improvement in #805.

A fix for r22811 has been posted: Patch #41678: Fix lost backward compatibility about return type of ProjectQuery#results_scope

Go MAEDA wrote in #note-40:

A fix for r22811 has been posted: Patch #41678: Fix lost backward compatibility about return type of ProjectQuery#results_scope

Fix committed, thanks!