Patch #16133
closed
- Target version changed from Candidate for next minor release to 2.5.3
I think this is a an easy one. Is it okay if I simply assign it to a target version?
This ties in with #17071 which adjusts the behavior of the watchers assignment so you can filter/search and not have to add them one at a time.
- Target version changed from 2.5.3 to Candidate for next minor release
I see the point but this change adds to much overhead for projects with lots of users.
- Related to Defect #22977: A project member has no access and gets no notification, when being a watcher of the issue added
- Related to Defect #24061: Tickets can be watched by users who are not available in specific tracker added
- Related to Feature #28368: regarding watcher added in private project but not getting notification added
- Related to Defect #30370: No validation when adding watcher who is not in this project added
- Related to Feature #5159: Ability to add Non-Member watchers to the watch list added
Here are some ideas in order to avoid the overhead:
1. If we really want to show some watchers in the new issue form:
- Get first 20 users from the database and check the visibility only for them
- Get more users from the database and check the visibility until we get 20 users that can watch the issue.
- Load them async.
2. If not, we just display the "Search for watchers to add" link to the user.
If we go for 1, we need also to load the watchers form when the tracker/project changes.
- Related to Patch #33329: Improve watchers functionality to mark the users that are watching a non visible object and to not return watchers that cannot see the object added
- Status changed from New to Closed
- Target version deleted (
Candidate for next minor release)
A similar fix has been merged in Redmine 4.2.0 (#33329).
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Toshi MARUYAMA 
Updated by 
Updated by 
Updated by