Feature #6375

Last updated by colum in issue list

Added by Alexander F over 6 years ago. Updated 23 days ago.

Status:ClosedStart date:2010-09-12
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Issues
Target version:3.4.0
Resolution:Fixed

Description

Hi,
I think that it will very beneficial if there was an "Last updated by" column in the issue list, so that way users will be able to tell if the issue was updated or not without entering their mailbox.

add_column_last_updated_by.patch Magnifier (3.42 KB) Marius BALTEANU, 2016-08-04 12:47

add_column_last_updated_by_v2.patch Magnifier (5.04 KB) Marius BALTEANU, 2016-08-04 12:53

6375_add_last_updated_by_column_r16248.patch Magnifier (6.85 KB) Marius BALTEANU, 2017-01-22 12:44

6375_add_last_updated_by_column_r16248_v2.patch Magnifier (7.09 KB) Marius BALTEANU, 2017-01-22 14:20

6375_add_last_updated_by_column_r16248_v3.patch Magnifier (7.02 KB) Marius BALTEANU, 2017-01-26 10:52

6375-screenshot.png (79.2 KB) Go MAEDA, 2017-01-29 15:17


Related issues

Related to Redmine - Feature #17720: Filter issues by "Updated by" and "Last updated by" Closed
Duplicated by Redmine - Feature #9127: Allow "Updated By" as a column in the issues list Closed 2011-08-25
Duplicated by Redmine - Feature #9550: Include Updated By and Update Date Time in Issue List(s) Closed 2011-11-11
Duplicated by Redmine - Feature #7660: Add the possibility to view the last updater of an issue Closed 2011-02-19
Duplicated by Redmine - Feature #22279: Need to get the last user who uptated an issue Closed
Duplicated by Redmine - Feature #11919: Issues list needs some kind of "last-modified-by" mark. Closed
Duplicated by Redmine - Feature #5294: Add a "last comment by" column to the issues list Closed 2010-04-12

Associated revisions

Revision 16366
Added by Jean-Philippe Lang 23 days ago

Last updated by colum in issue list (#6375).

Revision 16376
Added by Jean-Philippe Lang 23 days ago

Fix loading of last visible journal (#1474, #6375).

Revision 16377
Added by Jean-Philippe Lang 23 days ago

Preload journal's user (#6375).

History

#1 Updated by Alexander F over 6 years ago

Just a small correction - last updated by and not just "updated by".

Thanks.

#2 Updated by Mischa The Evil over 6 years ago

  • Subject changed from Updated by colum in issue list to Last updated by colum in issue list

Alexander F wrote:

Just a small correction - last updated by and not just "updated by".

I've modified the issue-properties to match the precise request.

#3 Updated by Victor Sheldeshov over 5 years ago

Does anybody a patch or any workaround?

#4 Updated by Victor Sheldeshov over 5 years ago

(Sorry!) "*Have* anybody..."

#6 Updated by Olivier Clavel almost 5 years ago

+1

#7 Updated by Vadim K over 4 years ago

+1

#8 Updated by Brandon Bonds over 4 years ago

+1

#9 Updated by A. G. almost 4 years ago

In case if anyone still interested: last_updated_by_column plugin adds "Last Updated by" column to:
  • Issues list (as extra column)
  • My page (as a separate component)

#10 Updated by Mike M Pestorich over 3 years ago

+1

The plugin above only partially works with Redmine 2.3.1.

1) The last updated by issues block when added "My Page" displays correctly but right clicking on an issue in it doesn't work.
2) On the main "/issues" page a "Last Updated By" column isn't availble as an option in "Available Columns" such that it could be moved into "Selected Columns" so that it would be displayed.

#11 Updated by A. G. over 3 years ago

Turns out Redmine 2.3.0 introduced changes that broke "Updated By" on ./issues page.
The updated version of the plugin takes that into account.

#12 Updated by M. B. almost 2 years ago

+1

Would be nice to have that in Redmine and not just as a plugin

#13 Updated by zar zar over 1 year ago

+1

This will be a very usefull feature. I hope it will be added soon!!!

Thanks

#14 Updated by Sunny Arge over 1 year ago

We want to see lastly our edited issues (last updated by) and we can inform people if the issue stays on them so much time etc.
Thank you.

#15 Updated by Florian Gruber about 1 year ago

+1
definitly more than eye candy

#16 Updated by Go MAEDA about 1 year ago

  • Duplicated by Feature #22279: Need to get the last user who uptated an issue added

#17 Updated by Go MAEDA about 1 year ago

  • Related to Feature #17720: Filter issues by "Updated by" and "Last updated by" added

#18 Updated by JW Fuchs 9 months ago

+1

#19 Updated by Joris Hartog 8 months ago

+1

For the people that want this as a plugin, this one works for me:

https://github.com/neowit/redmine_last_updated_by_column.git

#20 Updated by Marius BALTEANU 8 months ago

I made a patch (with tests) that implements the "Last updated by" as column in issues list. This patch should be applied after the patch from #17720 because it uses the same local as filter "Last updated by".

The patch has one limitation: sorting issues after "Last updated by" column is disabled because I wasn't able to add the sorting query to take into account the "Users display format" setting (in the plugin mentioned above, the user format for this column is hard-coded). Maybe a Redmine contributor can solve this limitation, but in my opinion the patch is useful also with this limitation.

#21 Updated by Marius BALTEANU 8 months ago

Added a new version (add_column_last_updated_by_v2.patch) that does not contain a unnecessary change presented in the first patch.

#22 Updated by Go MAEDA 3 months ago

  • Duplicated by Feature #11919: Issues list needs some kind of "last-modified-by" mark. added

#23 Updated by Go MAEDA 2 months ago

  • Duplicated by Feature #5294: Add a "last comment by" column to the issues list added

#24 Updated by Marius BALTEANU 2 months ago

I've uploaded a new version of the patch:
- it cleanly apply on the current trunk
- it checks for journal visibility
- fixes the limitation from the previous version of the patch (sorting by "Last updated by" column works now).

Unfortunately, I didn't do any performance test.

I think that it'll be great to deliver this issue along with #17720 and #1474 (there are at least 5 duplicate issues).

#25 Updated by Go MAEDA 2 months ago

Marius, thank you for updating the patch. I hope that this feature will be included in 3.4.0
But a test fails in my environment. Could you check the problem?

$ ruby test/unit/query_test.rb
(snip)

  1) Failure:
QueryTest#test_query_with_last_updated_by_column [test/unit/query_test.rb:1301]:
--- expected
+++ actual
@@ -1 +1 @@
-["User", "String", "String", "User", "String", "String", "String"]
+["User", "User", "String", "String", "String", "String", "String"]

186 runs, 527 assertions, 1 failures, 0 errors, 0 skips

My environment is as follows:

Environment:
  Redmine version                3.3.2.devel.16248
  Ruby version                   2.3.1-p112 (2016-04-26) [x86_64-darwin15]
  Rails version                  4.2.7.1
  Environment                    development
  Database adapter               SQLite

#26 Updated by Marius BALTEANU 2 months ago

Thanks Go MAEDA for testing the patch. I've attached the fixed version. The problem was generated by the data fixtures (journals weren't loaded by query_test.rb).

Jean-Phillipe Lang, I saw in r16228 that you preferred to generate the test data directly in the tests. It is better than using the existing fixtures?

#27 Updated by Go MAEDA 2 months ago

Thank you for the patch on #6375#note-26 but it still fails.

$ ruby test/unit/query_test.rb
(snip)

  1) Failure:
QueryTest#test_query_with_last_updated_by_column [test/unit/query_test.rb:1301]:
--- expected
+++ actual
@@ -1 +1 @@
-["User", "String", "String", "User", "String", "String", "String"]
+["User", "User", "String", "String", "String", "String", "String"]

186 runs, 527 assertions, 1 failures, 0 errors, 0 skips

#28 Updated by Marius BALTEANU 2 months ago

Thanks again for testing the patch. Something is wrong with my development instance.

I've attached a new version which passed the tests on both mysql and sqlite3 databases.

notroot@b8ae13776d3c:/work$ RAILS_ENV=test rake db:drop db:create && ruby test/unit/query_test.rb
/usr/local/bundle/gems/htmlentities-4.3.1/lib/htmlentities/mappings/expanded.rb:465: warning: duplicated key at line 466 ignored: "inodot" 
/usr/local/bundle/gems/htmlentities-4.3.1/lib/htmlentities/mappings/expanded.rb:465: warning: duplicated key at line 466 ignored: "inodot" 
/usr/local/bundle/gems/htmlentities-4.3.1/lib/htmlentities/mappings/expanded.rb:465: warning: duplicated key at line 466 ignored: "inodot" 
Run options: --seed 496

# Running:

..........................................................................................................................................................................................

Finished in 18.171939s, 10.2356 runs/s, 29.0008 assertions/s.

186 runs, 527 assertions, 0 failures, 0 errors, 0 skips

#29 Updated by Go MAEDA about 1 month ago

Thanks to Marius, the patch works fine as expected and passed all tests.
Ideally this feature whould be included in 3.4.0 along with #17720.

#30 Updated by Jean-Philippe Lang 23 days ago

  • Status changed from New to Closed
  • Assignee set to Jean-Philippe Lang
  • Resolution set to Fixed

Feature is added, thanks for the patch Marius. I've reworked the proposed changes a bit:
- Issue#last_updated_by returns nil instead of an empty string when there's no updates
- Issue.load_visible_last_updated_by loads only the last journals instead of loading all of them
- More robust unit test (I had random test failure)
- Functional tests

Also available in: Atom PDF