Project

General

Profile

Actions

Defect #9478

closed

User with groups may not see issues assigned to him or to its groups

Added by Igor Zubkov over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2011-10-26
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

At line source:trunk/app/models/issue.rb#L97

redmine building array with ids for Principals and then use them in building sql:

"(#{table_name}.is_private = #{connection.quoted_false} OR #{table_name}.author_id = #{user.id} OR #{table_name}.assigned_to_id IN (#{user_ids}))"

but if it missing .join(', ') and it miss issues which are assigned to user/group if user.groups more then one. b/c, ruby on [1, 2] do .to_s and we have "12", instead "1, 2".

The same for source:trunk/app/models/issue.rb#L100

Patch for revision r7655 attached.


Files

redmine-r7655-issue.patch (925 Bytes) redmine-r7655-issue.patch Igor Zubkov, 2011-10-26 17:50

Related issues

Has duplicate Redmine - Defect #9400: Private issues are not shown if the user is included in a group.Closed2011-10-10

Actions
Actions #1

Updated by Mischa The Evil over 12 years ago

  • Category set to Issues
Actions #2

Updated by Etienne Massip over 12 years ago

Could you please describe a buggy user situation?

Actions #3

Updated by Igor Zubkov over 12 years ago

Etienne Massip wrote:

Could you please describe a buggy user situation?

Sure.

We have:
Two Users, Two Groups and Project. In redmine settings -> Issue tracking -> enable "Allow issue assignment to groups".

First user is in two Groups. Second user create issue and assign to Group (doesn't matter first or second). First user can't see this issue in issue list, but can see know url to go. If First user is only one group, it works, user see issue in issue list.

Actions #4

Updated by Jean-Philippe Lang over 12 years ago

  • Tracker changed from Patch to Defect
  • Subject changed from Fix building sql for issue to User with groups may not see issues assigned to him or to its groups
  • Status changed from New to Resolved
  • Target version set to 1.2.2
  • Affected version (unused) set to 1.2.1
  • Resolution set to Fixed
  • Affected version set to 1.2.1

Fixed in r7771 with test, thanks for pointing this out.

Actions #5

Updated by Jean-Philippe Lang over 12 years ago

  • Status changed from Resolved to Closed
  • Target version deleted (1.2.2)
  • Affected version (unused) changed from 1.2.1 to devel
  • Affected version deleted (1.2.1)

Only trunk is affected. Group assignment is not present in 1.2-stable.

Actions

Also available in: Atom PDF