Feature #6375
closedLast updated by colum in issue list
Added by Alexander F almost 14 years ago. Updated about 7 years ago.
0%
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.
Files
add_column_last_updated_by.patch (3.42 KB) add_column_last_updated_by.patch | Marius BĂLTEANU, 2016-08-04 12:47 | ||
add_column_last_updated_by_v2.patch (5.04 KB) add_column_last_updated_by_v2.patch | Marius BĂLTEANU, 2016-08-04 12:53 | ||
6375_add_last_updated_by_column_r16248.patch (6.85 KB) 6375_add_last_updated_by_column_r16248.patch | Marius BĂLTEANU, 2017-01-22 12:44 | ||
6375_add_last_updated_by_column_r16248_v2.patch (7.09 KB) 6375_add_last_updated_by_column_r16248_v2.patch | Marius BĂLTEANU, 2017-01-22 14:20 | ||
6375_add_last_updated_by_column_r16248_v3.patch (7.02 KB) 6375_add_last_updated_by_column_r16248_v3.patch | Marius BĂLTEANU, 2017-01-26 10:52 | ||
6375-screenshot.png (79.2 KB) 6375-screenshot.png | Go MAEDA, 2017-01-29 15:17 | ||
paint.png (13.4 KB) paint.png | Last_updated_gives_error | Shreyas Moolya, 2017-06-27 13:50 |
Related issues
Updated by Alexander F almost 14 years ago
Just a small correction - last updated by and not just "updated by".
Thanks.
Updated by Mischa The Evil almost 14 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.
Updated by Victor Sheldeshov over 12 years ago
Does anybody a patch or any workaround?
Updated by A. G. over 11 years ago
- Issues list (as extra column)
- My page (as a separate component)
Updated by Mike M Pestorich about 11 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.
Updated by A. G. about 11 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.
Updated by M. B. over 9 years ago
+1
Would be nice to have that in Redmine and not just as a plugin
Updated by zar zar almost 9 years ago
+1
This will be a very usefull feature. I hope it will be added soon!!!
Thanks
Updated by Sunny Arge almost 9 years 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.
Updated by Go MAEDA over 8 years ago
- Has duplicate Feature #22279: Need to get the last user who uptated an issue added
Updated by Go MAEDA over 8 years ago
- Related to Feature #17720: Filter issues by "Updated by" and "Last updated by" added
Updated by Joris Hartog about 8 years 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
Updated by Marius BĂLTEANU about 8 years 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.
Updated by Marius BĂLTEANU about 8 years ago
Added a new version (add_column_last_updated_by_v2.patch) that does not contain a unnecessary change presented in the first patch.
Updated by Go MAEDA over 7 years ago
- Has duplicate Feature #11919: Issues list needs some kind of "last-modified-by" mark. added
Updated by Go MAEDA over 7 years ago
- Has duplicate Feature #5294: Add a "last comment by" column to the issues list added
Updated by Marius BĂLTEANU over 7 years ago
- File 6375_add_last_updated_by_column_r16248.patch 6375_add_last_updated_by_column_r16248.patch added
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).
Updated by Go MAEDA over 7 years 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
Updated by Marius BĂLTEANU over 7 years ago
- File 6375_add_last_updated_by_column_r16248_v2.patch 6375_add_last_updated_by_column_r16248_v2.patch added
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?
Updated by Go MAEDA over 7 years 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
Updated by Marius BĂLTEANU over 7 years ago
- File 6375_add_last_updated_by_column_r16248_v3.patch 6375_add_last_updated_by_column_r16248_v3.patch added
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
Updated by Go MAEDA over 7 years ago
- File 6375-screenshot.png 6375-screenshot.png added
- Target version set to 3.4.0
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.
Updated by Jean-Philippe Lang over 7 years 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
Updated by Go MAEDA over 7 years ago
- Category changed from Issues to Issues list
Updated by Shreyas Moolya about 7 years ago
For the people that want this as a plugin, this one works for me:
https://github.com/neowit/redmine_last_updated_by_column.git
In my case it didn't work.
'My Page' gives error
Updated by Go MAEDA about 7 years ago
- Has duplicate Feature #5791: Set latest journal(log) id when an issue updated (in a issues table) added