The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Customer participation in Change/Release Management
I work in the IT department in a company of 250+ users (customers) We have a an internal policy on requesting Software implementation (Change management) or updates/patches (Release Management). ...
ITIL describes the use of Change Advisory Boards typically populated by non-it personnel.
In order to align properly with the ITIL framework it would make sense to allow for the creation of CAB's as logical objects in GTA.
I would argue that the participation of an employee in a CAB is the extension of ITIL into the business no different than allowing a user to report an incident and therefore should not need to be tied to a licensed account.
But when it comes to GTA so much of the ITIL framework has been watered down to make the product more palatable perhaps strict alignment isn't the goal.
In order to align properly with the ITIL framework it would make sense to allow for the creation of CAB's as logical objects in GTA.
I would argue that the participation of an employee in a CAB is the extension of ITIL into the business no different than allowing a user to report an incident and therefore should not need to be tied to a licensed account.
But when it comes to GTA so much of the ITIL framework has been watered down to make the product more palatable perhaps strict alignment isn't the goal.
