Change Roles - Bravo! Feedback and Enhancement Requests

(Written with respect to experiences in ServiceDesk Plus build 9003 Enterprise - upgrading to 9010 shortly)

First, I would like to applaud the use of Change Roles. Combined with Change Workflows and permissions afforded to Roles, this allows automated notification to be sent to whichever ServiceDesk Plus user fills the Change Role for a particular Change. Bravo!

Please forgive me if someone has proposed them already, but I would like to suggest enhancements to the Change Roles feature.

Request 1: Please! Make assigning a Change Role in the Change Record easier to use!

Every user of the new Change module features has given me immediate feedback as soon as they have to assign someone to a Change Role - ease of use is an issue!

Proposed enhancements:

Auto-completing the name as you type (as in notification composition window 'To:' and 'CC' recipient fields) would be an enormous step forward. Additionally, once you select/delete the appropriate users from the list, and select OK, the interface should save the selections in the field - not require you to additionally select the tiny green checkmark next to the field to save the list a second time. The next enhancement request will also help narrowing search results...

Request 2: Be able to configure a Change Role to allow only a specific group of randomly selected users (instead of just Technicians and/or Requesters)

Build 9003 capability:
Currently you can only lock down which users can use 'ChangeManager' Change Role permissions (the person in this field must be assigned the overall user Role 'SDChangeManager'). The way that all other Change Roles are built currently can lead to mistakes when granting Change Roles that have restricted access. (i.e. I can restrict the list to Technicians but can accidentally select a Technician who should NEVER be a LineManager as a LineManager, and that person will receive automated notifications containing instructions for work on the Change Record, and edit/approve permissions they should not have.)

Proposed enhancement:

Change Roles could be configured to allow the following scenarios:

a. All Users (Requesters and Technicians)

b. Technicians only

c. Requesters only

d. Specfically selected group of Requesters/Technicians

Request 3: Configuration to define which Status Actions a Change Role can use in a Stage

Our organization's Change Management process has several 'Status'es during the Planning stage of the Change, and an organized workflow where each Change Roles is allowed to transition to another Status.

Build 9003 capability:

Currently a Change Role user will see all edit Status Actions in a Role, not just the ones that they are supposed to use according to the organization's SOP.

Proposed enhancement:

It would be a great help if Change Role assignees if we could restrict the Status Actions that they can use for each Stage (i.e. our LineManager should be able to use Status Action B to transition to Status B, but should never be allowed to use Status Action C, D, or E in the same Stage because Status Action C is the responsibility of the ChangeOwner who got the automated notification when Status Action B was selected, Status Action D is the responsibility of the ChangeManager who got the automated notification when Status Action C was selected, etc.)