Hi Scott Hildebrand,

You are right, I also had the same problem. In redmine, there is no way to track who all users were involved in a tracker. Mostly developers who resolves issues have to reassign tracker to author so that it get verified by same(i.e. tester). To handle this, I made a custom field called 'Resolved By'.

I think, one of the problems you mentioned above can be handled by this plugin http://www.redmine.org/plugins/involvement_filter

But these features need to incorporated in Redmine core. I request Redmine team to consider these issues as soon as possible.
--------------------------------------------------------------------------------
Thanks Lajish! It seems to be working for version 2.4.2, except for some missing translations which is no biggie. This is the plugin for 2.x that I'm using: https://github.com/commandprompt/redmine_involvement_filter
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
+1
These 2 filters would make sense for us too.

For example: List all the open issues I have modified since "that day". We can have all the opened issues modified since "that day", but not the ones (last) modified by _a specific user_.

--------------------------------------------------------------------------------
Are there any options for this filter "updated by" for Redmine v.3.x. ?
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
I made a patch (with tests) that adds these 2 useful filters:

# *updated_by*: it can be used to find tickets updated or not by specific project users
Use case: Find all the tickets that have been updated (touched) by me.
# *last_updated_by*: it can be used to find tickets that were last updated or not by specific users
Use case: Find all the tickets that have been last updated by user x (a customer for example).

Both filters apply only on issues with at least one update made after issue creation.

Because the "last_updated_by" filter expects that the issue updated_on date to be equal with last journal created_on date, it was required to make some changes to issues fixtures and journal fixtures in order to match the dates. If i'm wrong with this expectation, please let me know and I'll try to find another solution.

Also, I've added a new journal entry in journal fixtures to test a scenario (with "!" operator). Because of this new journal entry, I changed in issue_test the issue id of the ticket without journals.

I'll add another patch that implements the last_updated_by as column in #6375.

--------------------------------------------------------------------------------
Thanks for submitting the patch, Marius BALTEANU. This is very useful.

It works fine for me and passed all tests. Setting target version to 3.4.0.

--------------------------------------------------------------------------------
Updated the patch to cleanly apply on the current trunk. All the tests pass.
--------------------------------------------------------------------------------
Rebased on r15949 v2 patch with minor fix.

<pre><code class="diff">
diff --git a/test/unit/query_test.rb b/test/unit/query_test.rb
--- a/test/unit/query_test.rb
+++ b/test/unit/query_test.rb
@@ -29,7 +29,7 @@
:queries,
:projects_trackers,
:custom_fields_trackers,
- :workflows
+ :workflows, :journals
</code></pre>
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Updated the patch to cleanly apply on the current trunk.

@Jean-Philippe Lang, is there anything I can do in order to have this committed?
--------------------------------------------------------------------------------
For users who are not allowed to view private notes, these filters can match issues even if the update is not visible to the user.

Eg. user A updates issue X with private notes, user B (who is not allowed to view private notes) filters issues updated by user A and sees issue X in the results. But he won't see any update by user A when looking at the issue history.

Is it an acceptable behaviour?
--------------------------------------------------------------------------------
Jean-Philippe Lang wrote:
> For users who are not allowed to view private notes, these filters can match issues even if the update is not visible to the user.
>
> Eg. user A updates issue X with private notes, user B (who is not allowed to view private notes) filters issues updated by user A and sees issue X in the results. But he won't see any update by user A when looking at the issue history.
>
> Is it an acceptable behaviour?

Very good question :)

From my point of view, this is an acceptable behaviour because the privacy of the note is not affected. User B it'll see only that the issue X was updated by user A. Currently, you can see the last update date, but without seeing the respective update in the history:

!updated.png!

In the same time, I agree that the behaviour can be a little bit confusing for the users.

My proposal is to implement them as it is and see if the users will complain about it.
--------------------------------------------------------------------------------
Because I've mix feelings about my previous proposal, I'm going to take some feedback this week from our users regarding the expected behavior.
--------------------------------------------------------------------------------
I don't have a clear resolution after the feedback received, some of our users consider the behavior acceptable, and others agree that can be a little bit confusing.

Considering that is quite complex to ignore the private updates depending on the user permissions (with my Ruby/Redmine skills), and that the chances to find the issues updated by A to which user B doesn't have access are low, I think it is an acceptable behavior at least in the first phase.

--------------------------------------------------------------------------------
Thanks for your feedback Marius.
I think hiding private updates is a better option and was not so difficult to implement without too much changes. It's committed in r16228. I've made a few tests with Postgres and 1M journals without performance issues. Please let know how it works for you.
--------------------------------------------------------------------------------
Sorry for reopening this issue.

I think it would be better to change the position of "Updated by" and "Last updated by" in the filters drop-down. Here is a patch: attachment:17720-change-filter-position.diff

Please see the following images for details.

*Before (current implementation):*
!filter-position-before.png!

*After:*
!filter-position-after.png!
--------------------------------------------------------------------------------
Committed, thanks.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Jean-Philippe Lang wrote:
> I think hiding private updates is a better option and was not so difficult to implement without too much changes. It's committed in r16228. I've made a few tests with Postgres and 1M journals without performance issues. Please let know how it works for you.

Thanks for committing this new filters and for the journal visibility implementation. I test it and it works great for us. Unfortunately, I don't have a large MySQL database for tests, but I'll let you know if we have any performance issue on our instance after 3.4.0 release.

Speaking about 3.4.0 and a little bit off-topic, do you have any estimation about the release date? There are a lot of great features already committed :).

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

relates,Closed,17932,[Feature Request] History Assignee filter
relates,Closed,6375,Last updated by colum in issue list
relates,New,10943,Query issues based on activity history
relates,Resolved,10975,An 'Involved In' filter
duplicates,Closed,23210,"Updated by" filter is needed
duplicates,Closed,1882,filter issues "modified by" a user
duplicates,Closed,13727,Search option 'updates made by me'
duplicates,Closed,2333,Add ability to search for issues that the user touched