Hello, that's exactly what I followed. My first impression is that with such a setup, changes cannot be created/executed in a sane way. I'm a developer myself, so conditions and actions are not foreign for me, but if I have to define this huge number of conditions for each change I have to manage, that's a bit of an overkill (even with using templates). However, it is likely that I didn't understand the whole change thing in ITSM :-) Isn't it a bit over-complicated?
Best, Gergely On 14 Apr 2014 16:15, "Florian Edlhuber" <florian.edlhu...@gmx.de> wrote: > Hi, > > 14.04.2014 14:57 - Gergely Polonkai schrieb:Hello, > > is there anyone on this list who has successfully implemented a Change > > in ITSM 3.x? > > Yes. :) > > > I have tried and tried, but cannot go forward from requested > > to approved state. Is there a fully blown tutorial on this? > > > See > http://otrs.github.io/doc/manual/itsm/3.3/en/html/ch08s05.html#idp37007488 > and in detail the conditions actions section. > > you can not set a state without conditions/actions. > > (there is a test scenario sysconfig setting...) ;) > > Florian > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs >
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
