I'd really like tasks to inherit their permissions from the assigned project. Currently all new tasks are visible and editable for "all users" (I assume the public visibility option is gone because I disabled public access itself).
Steps to reproduce
- View a project
- Click Edit
- Change the permissions menus to the project's members (the group of the same name at the bottom of the list).
- Create a new task
- Default setting is visible to and editable by all users
The task would be visible only to the members of the specified project (or projects).
Manually change the menus when creating a task (or afte the fDct).
UPDATE: I realized "create another" saves the permissions settings to I have a decent workaround when adding multiple items with repetitive unique permissions. It's not as tight as I'd like but it helps a lot.
I come from a system where a task can only be assigned to a single project, which certainly makes this much simpler to implement. I like the idea of multiple projects, and wish it would derive these permissions from the union of the task's projects.
I prefer to keep some projects within a small team during germination before opening it up to a larger group of folks for development.
Separately, this would be more acceptable if I could change permissions on the bulk edit screen, which doesn't seem to be the case.
I hope I'm totally nuts and that this type of automatic inheritance is possible, otherwise I'm happy to file another bug requesting permission options to the bulk edit screen.