Open nickbe opened 8 years ago
I reuploaded the list now.
Although I've spent an impossible amount of time compiling and trying to think like a maniac about the details, it's really not finished yet. (and i thought this shouldn't take much more than an hour or two :stuck_out_tongue_winking_eye: )
But I'd say it's enough to look through it and start verifying its items together now :smile:
Ah and btw. I'm convinced that most (if not all) of all that is already working.
Ok I'm back on duty now. First thing for me is complete the roles and rights above and get back into tinyissue as fast as possible :)
Ok. done. I think the list is now rather complete. And I also think that many, if not most things are already working here. If there's anything unclear please ask right away.
These fields/flags should be additionally stored per project
Public projects
Users with an otherwise active login do not have to be project members to participate (typical for public software support)
Private projects
Users have to be assigned to a project to participate (typical for development groups/open source projects and suchlike)
Internal projects
Assigned users have limited and confidential access to projects and issues (typical for custom client projects)
So who can do what?
Please note that almost all lists and complete issue visibity or editing is always depending on the tag role limits. Maybe a user would be allowed to edit his/her own ticket but cannot because the current status tags readonly role limit says he can't.
Detailed role matrix:
Remarks:
If a developer is able to edit/work with an issue does NOT depend on his assignment alone, but is controlled by the different status tags. Example: He's already assigned to an issue - but he's not allowed to see issues with the status 'NEW' and 'CONFIRMED'. But then as the status is changed to 'OPEN' he can see the issue.
NOTES ON PROJECT OWNERSHIP
Any manager/admin who creates a project is it's owner. Being an owner is treated equally to being assigned, with the special rule that a manager cannot revoke an owner from his project (not even himself) - an administrator on the other hand can do this.
These actions are administration only
Manager (and Admins because they're also managers)
I think this list should now be rather complete.