Permission that uniquely controls assignment of tickets to milestones
|Reported by:||Ryan J Ollos||Owned by:||Ryan J Ollos|
I have found that the
MILESTONE_VIEW permission allows a user to change the milestone with which a ticket is associated. That is, it causes the milestone drop-down list to be populated with the milestones and allows the user to change which milestone a ticket is associated with.
It seems incorrect for a
*VIEW permission to grant a change action. Also, it seems desirable to allow a user to view milestones, but not change the milestone assignment for a particular ticket. In my situation, the configuration control board (lead software developers) are in charge of assigning tickets to milestones, and it would be better if all users with
MILESTONE_VIEW permissions did not have this level of control.
Therefore, it would be nice to have a separate permissions to control the assignment of tickets to milestones. This permission should be named either
MILESTONE_ASSIGN_TICKET. I suspect the former is a better fit for the permissions naming schema (See: TracDev/Proposals/EvenFinerGrainedPermissions).
Note, this permission should be different than the
MILESTONE_MODIFY, which controls modifying the description, due date, and other milestone data.
Change History (17)
comment:1 by , 10 years ago
|Summary:||Permission to uniquely control assignment of tickets to milestones → Permission that uniquely controls assignment of tickets to milestones|
comment:11 by , 3 years ago
|Milestone:||next-major-releases → 1.2.1|
|Status:||new → assigned|
comment:14 by , 3 years ago
|Status:||closed → reopened|