Functionality for ConfigItem state?
Hello list,
I was wondering what is the use of the functionality (productive, postproductive, preproductive) field for the ConfigItem state? Are there some checks going on in other parts of the application that makes it act differently depending on the functionality? I was thinking that it might make it impossible to link ConfigItems that are postproductive to ticket but *unfortunately* that is not the case.
Hallo
If a config item have the state "Retiered" (postproductive), it was hide in all overview masks.
It exists no difference between "productive" and "preproductive" in OTRS::ITSM 1.0. But we need the functionalities "productive" and "preproductive" in future version.
Best regards, Manuel Hecht
((otrs)) :: OTRS GmbH :: Europaring 4 :: D - 94315 Straubing Fon: +49 (0)9421 56818 0 :: Fax: +49 (0)9421 56818 18 http://www.otrs.com/ :: Communication with success!
-----Ursprüngliche Nachricht----- Von: itsm-bounces@otrs.org [mailto:itsm-bounces@otrs.org] Im Auftrag von Wouter Peschier - Hostnet Internet Gesendet: Freitag, 22. Juni 2007 14:29 An: itsm@otrs.org Betreff: [itsm] Functionality for ConfigItem state?
Hello list,
I was wondering what is the use of the functionality (productive, postproductive, preproductive) field for the ConfigItem state? Are there some checks going on in other parts of the application that makes it act differently depending on the functionality? I was thinking that it might make it impossible to link ConfigItems that are postproductive to ticket but *unfortunately* that is not the case.
_______________________________________________ OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm Support or consulting for your OTRS::ITSM system? => http://www.otrs.com/
participants (2)
-
Manuel Hecht -
Wouter Peschier - Hostnet Internet