Hi, Konstantin. The ideal way would be to engage a new ITSM 3.0 functionality with change management. After all, a change is the process to transform a CI from one state to another.
Meanwhile you can link tickets to a CI and view linked tickets in the bottom part of CI display Anton. 2010/3/11 Konstantin S. Ershov <[email protected]> > Hi, everyone! > > Could anyone please share with the best way of maintaining a journal > for config items? E.g. I'm upgrading some software on a server and I'd > like my collegues to see all the activity related to this server. > > Am I right that I can do it just creating a new ticket and linking it with > CI? > > Thanks in advance! > --------------------------------------------------------------------- > OTRS mailing list: itsm - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/itsm > To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm > > NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! > http://www.otrs.com/en/support/enterprise-subscription/ >
--------------------------------------------------------------------- OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/
