What about setting the state only via conditiones( = not manually), and then defining conditions where only a certain role can approve and all other workorders are locked until its done. As you need 3-5 definitions average for every workorder, templates might be a good idea.... Nils Leideck wrote:

Not possible yet.

On 26.10.2012, at 23:01, padawan wrote:

...

Hello,

I'm getting the grip on otrs, albeit quite a newbie for now...

I have configured two roles: "Change Managers" and "Support"; the first is member of the default group "itsm-change-manager", the second is member of "itsm-change-builder", and of course few agents associated with a role or the other.

I would like to disable the change of state "Approved" and/or "Rejected" for agents belonging to the role "Support", I would like to give only to the change managers the possibility to approve/reject.

Essentially my problem is that any agent with permissions to create a change, can also change its status into approved.

Thanks in advance for any help :)

Regards, Sono

--------------------------------------------------------------------- OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm

-- Cheers, Nils

http://webint.cryptonode.de / a Fractal project

------------------------------------------------------------------------

--------------------------------------------------------------------- OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm

-- Sent from my Android phone with K-9 Mail. Please excuse my brevity.