As a trainer I want to plan our resources according training appointments in the calendar module. To manage the trainers, you can use the resource planning feature addon. To manage objects, e.g. laptops for the trainings, you would have to create agents for them. It would be great if I could select objects (e.g. as ConfigItems from the CMDB) as resources for the appointments in the calendar.
It would be great if OTRS Reports Module could generate "Dynamic List" kind reports. Today it is not possible.
Another alternative way to get lists of CIs is that the Search functionality in the CMDB could use a Multiple Selection Field, to be able to perform searches over several CI classes at once.
It would be handy to have a back end script similar to otrs.ITSMConfigItemDelete.pl that would allow you to purge old CI versions. The xml_storage table does not seem to work very well when it gets large and people using automatic population of the CMDB can end up with a lot of versions that may not be required. We've done this manually on our CMDB by using a vbscript already, however it would be a useful addition to... more »
I need to set up different permissions to CIs in the same class. It could be made by allowing changing of group definition made for a class inside specified CI. Another idea is to allow defining permission to CIs per it's Type.
I need to allow to my customer user to see defined part of CMDB. Most important is to show him CIs which have the Customer user in Owner field. Another need is to show CIs linked with services customer uses. For example to allow read some parts of documentation stored in CMDB.
will be nice to have a kinda of filter like the actual just used in agent list filtering for CI's assets
It should be possible to sort ConfigItems by name in Overview. Sorting by ConfigItem# doesn't make any sense.
I suggest to improve the way classes and sub-classes are shown on AgentITSMConfigItem, and make them look like queues and sub-queues are shown. When building a large CMDB, it's neccesary to create sub-classes inside classes. Since OTRS creates sub-queues and sub-services on database using the parent::child syntax, it's easy to think this is the way sub-classes on CIs should be created so we have a Servers class and then... more »