Feature #2055
closed
Assigned to list for parent project in issue filter missing users of child projects
Added by Ewan Makepeace over 15 years ago.
Updated over 5 years ago.
Description
If I list issues for a parent project I cant filter by Assigned To if the user concerned is not a member of the parent project - even though I see their name in the list of issues they are not in the drop down menu.
Files
- File 2055_svn.diff added
- Category set to Issues
- Affected version (unused) set to devel
Proposition of patch attached, with some unit tests.
I still have a doubt on how private projects work, so maybe it has to be refined : let's say you have a public project with a private subproject. For the moment, you see issues of the subproject in the main project, so it's OK if users of this subproject appear in the filters. But maybe it's not desired behaviour...
If the parent project is public and the child project is private, you shouldn't be able to see any of the child project's issues.
Ok, I was admin so my test was wrong. I have to refine the patch.
New patch, adapted to respect project privacy. I'd like somebody to test it before it is integrated..
- File deleted (
2055_svn.diff)
- Tracker changed from Defect to Feature
- Status changed from New to Closed
- Resolution set to Duplicate
- Is duplicate of Feature #10126: Add members of subprojects in the assignee and author filters added
What are the odds that 10 years later:
- I am still on the same email address,
- The project is still alive and healthy
- I am still using Redmine (and this exact feature come to think of it) daily?
Gave me a bit of a thrill to see this.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by