Currently there is no easy way to allow for a Windows/AD Group to execute a job without elevating its rights to the SQLAgentOperatorRole or building a custom workaround.
I would like to allow any specified Windows/AD Group identical functionality as UserA outlined in the following situation:
UserA owns Job1 and is a member of the SQLAgentUserRole role. UserA can start/stop/modify/disable/enable Job1 at his/her leisure, but cannot create new jobs, delete jobs, or view/modify jobs he/she does not own.
I am requesting a way to allow for a Windows/AD Group to have the same functionality as UserA listed in the situation above. Currently I can do this with a SP and ownership chaining, but for the basic user that likes to use the UI, this is a rather cumbersome workaround.