Change Request

Evgeni,

we have following:


Change request is defined by us as a change on existing system or new request -- but not a indicent. We put in the requestor and attach if available a document. Changes always handled with Activities, because we have to have a estimation on time, costs and qualtiy before approval -- which is not available on Tickets. Approval is done by status. Date and work is entered in validated. In the case, an incident or a risk is source of change request, we link the Ticket or Risk, Action, Meeting, Decision, ... as origin.


Klaus

Thanks Klaus, but I would say this is kind of way around rather than solution. Change request can be raised by different ways and it need to be dealt with in consistent way - Initial CR document itself with description, estimates, etc. need to lead to a Ticket wich should have an aproval process by the different people before Activity will be created (can be rejected as well). Actually Ticket needed to link CR document to the Activity (if approved) or just keep it (in case of deferred) for future, or close it if rejected.
Regards,
Evgueni

Thanks - this definitely will help
Regards,
Evgueni

Hi Babynus,

if you add planned work, it would be welcome, if it is in the same manner as on Activities - requested, validated, planned, real -- for Date and work.

Klaus

Yes, I think everybody would like it this way! Will become very useful feature!
Regards,
Evgueni