Tools (SSMS, Agent, Profiler, Migration, etc.)
Multiple ideas here as follows:
1) Allow a Windows Group to Own a Job (I understand this would probably break a lot of existing security ownership rules)
2) Create a new ownership object, "Group Owner", that allows you to assign a Group ownership of a job.
3) Revamp SQL Job security model to more closely emulate DB security model (e.g. Grant permissions to a user/group to Update/Edit/Delete/Run any/specific jobs currently hosted on an instance as opposed to using the MSDB JobAgent roles).
Set the product above it's peers in regards to the security model. Won't take much on this but ease of administration isn't pitched nearly as much as it should be when comparing SQL Server to it's RDBMS peers.