Defect #36446
closed
Watchers autocomplete fails with 403 error when the search is made from multiple objects with different projects
Added by Dmitry Makurin almost 3 years ago.
Updated almost 3 years ago.
Description
Autocomplete is broken when bulk adding watchers for issues from different projects.
How to reproduce:
1. Open /issues.
2. Select two issues from different projects.
3. Press RMB.
4. Watchers => Add.
5. List of users will be shown.
6. Try to filter users.
This is happens because WatchersController can't find project for New and Autocomplete_for_user actions and authorize a user.
Files
- Tracker changed from Patch to Defect
- Category set to UI
- Status changed from New to Confirmed
Confirmed the issue. WatchersController#autocomplete_for_user returns 403 and the autocomplete does not work.
Started GET "/watchers/autocomplete_for_user?object_type=issue&q=dave" for 127.0.0.1 at 2022-01-19 11:42:57 +0900
Processing by WatchersController#autocomplete_for_user as */*
Parameters: {"object_type"=>"issue", "q"=>"dave"}
Current user: admin (id=1)
Rendered common/error.html.erb (Duration: 1.2ms | Allocations: 228)
Filter chain halted as :authorize rendered or redirected
Completed 403 Forbidden in 17ms (Views: 2.5ms | ActiveRecord: 10.8ms | Allocations: 1896)
- Target version set to Candidate for next minor release
- Assignee set to Marius BĂLTEANU
- Target version changed from Candidate for next minor release to 4.1.6
- Status changed from Confirmed to Resolved
- Resolution set to Fixed
- Target version changed from 4.1.6 to 4.2.4
Changing target version to 4.2.4 because the change has conflicts on 4.1-stable.
- Subject changed from Autocomplete for users fails with 403 error to Watchers autocomplete fails with 403 error when the search is made from multiple objects with different projects
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by