Redmine

I don't know if it will help but I'm facing the same situation. I would like to have several customers' groups to have access to the same project without viewing each other's groups issues. Currently it does not seem possible and the only workaround I see is to organize these kind of 'multi-customers' projects on a customers basis rather than on a projects one. But I'm a Redmine newbie, I may find other solutions. :)

Could also be related to Feature #7867

Rupesh, you can assign issues to a group. So that all people from the group will see it. With the "Issues assigned / Created by User" rule, the other groups won't see this issue. The 'bad side' is that you need to remove the assignment right if you want to keep confidential the other groups having access to this project.

The patch is OK, I don't know why it isn't already included in the stable release . It should be included as soon as possible !

Frédéric Senault wrote:

If it's of use, I'm also in the same situation ; I've attempted to implement this with the attached patch (against 2.5.1), and it seems to work.

Hi, how can I use the group filter after I attached this patch? Thanks.

+1

We also need such feature and doesn't seem so hard to implement.
Is there a road map for this? Why proposed patch hasn't been included in a release?

Patch #16195-6 works for me in Redmine 3.3.1, 3 years after it was written. Thanks Frédéric Senault. To my opinion, this should be added to stable redmine.

Patch #16195 don´t work for me in Redmine 3.0.3, anyone can help me about changes to the patch so can work on this version?

We are very interested in this issue. We work in Redmine 3.4.6. Is there any posibility of updating this patch or to include this funcionality in current release?

Rupesh Helwade wrote:

May be related to Feature #16074 request

We have 3 options for each role Issue Visibility,

1. All issues
2. All non-private issues
3. Issues assigned / Created by User.

How can the users from same group see each others issues, yet they are deprived of seeing issues from other groups.

Consider :
I have a Project named "The Project" with tracker as "Tickets"

We have 4 users user1, user2, user3 and user4.
We have two groups:
"Our Group" has user1 and user2
"Their Group" has user3 and user4

user1 and user2 should be able to see each others issues but not of user3 and user4 and vice versa.

With current visibility permissions I do not see solution to this.

Hence we can add new Issue visibility Permission as
"View Issues within current users' group"

By any chance, this feature can be added in a stable release ?

+1 for this ticket. need it for redmine version 4.

useful for a help desk where different company departments are reporting tickets but only should be able to see tickets from their own department.

+1 Great feature.

+1 Great feature.

Michael Michalewicz wrote:

Just implemented the patch to Redmine 4.1.1
Works with one exception.
User1 and User2 are in the same group.
User1 creates an issue.
User2 creates an issue.

When User1 logs in, he / she can see own issues and can see details of issue, can see the second issue created by user2 on list, but when the user try to click on the issue for more details, gets an authorization error.
The other way around the same.

OK, now I know what I missed.
The Group of the user must be assigned to the issue.
Sorry for the mistake.

Is there any option to make this more as the Group of Users that are assigned to the specific group?
so that the issues can be assigned to anybody, but user within the same group of user will see the issue on list and the details of progress?

Michael Michalewicz: Did you resolve problem with this patch on new redmine? f.e. 4.0.7 or 4.1.1? Since I've patched 4.0.7 I have 403 when I change Issues visibility to 'Issues created by or assigned to the user's group(s)' and try to open any own issue.

Resolved, this that piece of code for issue.rb for redmine 6.1.1:

         when 'group'   #SAURO
            user_ids = ([user.id] + user.groups.pluck(:id).compact + user.groups.map(&:users).flatten.pluck(:id).compact).uniq
            "( #{table_name}.author_id in (#{user_ids.join(',')}) OR #{table_name}.assigned_to_id IN (#{user_ids.join(',')}))" 
[..]

          when 'group' #SAURO
            user.groups.map(&:users).flatten.uniq.inject(false) { |p, u| p ||= (self.author == u || u.is_or_belongs_to?(assigned_to)) }