Defect #9478
closed
User with groups may not see issues assigned to him or to its groups
0%
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
Related issues
Updated by
Updated by Etienne Massip about 13 years ago
Could you please describe a buggy user situation?
Updated by Igor Zubkov about 13 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.
Updated by Jean-Philippe Lang about 13 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.
Updated by Jean-Philippe Lang about 13 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.