Can I change the "'add Change"-form in order to select a CI from a list(the CMDB), and ensure that the RfC will be linked to that CI?
Thanks in advance
/Eivind
How to relate a CI to a 'Add Change'
Moderator: crythias
-
- Znuny newbie
- Posts: 4
- Joined: 12 Sep 2011, 12:18
- Znuny Version: 3.09
- Real Name: Eivind Bengtsson
- Company: DMI
-
- Znuny advanced
- Posts: 106
- Joined: 13 May 2011, 14:47
- Znuny Version: 2.4 / 3.x
- Real Name: Lorenzo Marschall
- Company: bmsoft information technologies GmbH
- Location: Germany, Italy
- Contact:
Re: How to relate a CI to a 'Add Change'
RfC is linked to a change through the ticket. Means ticket (type rfc) => add change in ticket action => new change.
Linking config items to change can be done by extending Core::LinkObject => a combination Object1 ITSMChange and Object2 ITSMConfigItem and Type of your choice. To integrate it to AgentITSMChangeAdd you need to change the form. At least AgentITSMChangeAdd;ConfigItemID=x way did not work when I tested it last time analog to AgentITSMChangeAdd;TicketID=x
Linking config items to change can be done by extending Core::LinkObject => a combination Object1 ITSMChange and Object2 ITSMConfigItem and Type of your choice. To integrate it to AgentITSMChangeAdd you need to change the form. At least AgentITSMChangeAdd;ConfigItemID=x way did not work when I tested it last time analog to AgentITSMChangeAdd;TicketID=x
OTRS + ITSM + PostgreSQL @ Debian
Re: How to relate a CI to a 'Add Change'
CIs will be linked to the workorders typically
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 4
- Joined: 12 Sep 2011, 12:18
- Znuny Version: 3.09
- Real Name: Eivind Bengtsson
- Company: DMI
SOLVED: Re: How to relate a CI to a 'Add Change'
Hi
I managed to make the Core::LinkObject thing pissoble both ways. So now I can "Link" a Config Item to a "Change" from the CI view. By selecting the "Link" and on the link page choose "change" from the dropdown menu, that also lets me link to other CI's and tickets, services and workorders. The other way around I can choose a CI to linkt to from a ticket...
The solution for me was :
- To extend the Kernel/Config/Files/ITSMCore.xml
<!-- EBE -->
<ConfigItem Name="LinkObject::PossibleLink###3421" Required="0" Valid="1">
<Description Translatable="1">This setting defines that a 'ITSMChange' object can be linked with 'Ticket' objects using the 'Normal' link type.</Description>
<Group>Framework</Group>
<SubGroup>Core::LinkObject</SubGroup>
<Setting>
<Hash>
<Item Key="Object1">ITSMChange</Item>
<Item Key="Object2">ITSMConfigItem</Item>
<Item Key="Type">Normal</Item>
</Hash>
</Setting>
</ConfigItem>
<!-- EBE -->
<!-- EBE -->
<ConfigItem Name="LinkObject::PossibleLink###3422" Required="0" Valid="1">
<Description Translatable="1">This setting defines that a 'ITSMChange' object can be linked with 'Ticket' objects using the 'Normal' link type.</Description>
<Group>Framework</Group>
<SubGroup>Core::LinkObject</SubGroup>
<Setting>
<Hash>
<Item Key="Object1">ITSMConfigItem</Item>
<Item Key="Object2">ITSMChange</Item>
<Item Key="Type">Normal</Item>
</Hash>
</Setting>
</ConfigItem>
<!-- EBE -->
- To enable it in sysconfig > Core::LinkObject - Framework (two new boxes)
Actually quite easy..
Now for the next challenge - how do I make it possible to link (preferably mandatory) from a new Ticket to an existing CI ?
Regards
/Eivind
PS - thanks a lot to Lorenzo - it was his answer that got me in the right direction
PPS - how do I make this change survive future upgrades of the ITSM ?
I managed to make the Core::LinkObject thing pissoble both ways. So now I can "Link" a Config Item to a "Change" from the CI view. By selecting the "Link" and on the link page choose "change" from the dropdown menu, that also lets me link to other CI's and tickets, services and workorders. The other way around I can choose a CI to linkt to from a ticket...
The solution for me was :
- To extend the Kernel/Config/Files/ITSMCore.xml
<!-- EBE -->
<ConfigItem Name="LinkObject::PossibleLink###3421" Required="0" Valid="1">
<Description Translatable="1">This setting defines that a 'ITSMChange' object can be linked with 'Ticket' objects using the 'Normal' link type.</Description>
<Group>Framework</Group>
<SubGroup>Core::LinkObject</SubGroup>
<Setting>
<Hash>
<Item Key="Object1">ITSMChange</Item>
<Item Key="Object2">ITSMConfigItem</Item>
<Item Key="Type">Normal</Item>
</Hash>
</Setting>
</ConfigItem>
<!-- EBE -->
<!-- EBE -->
<ConfigItem Name="LinkObject::PossibleLink###3422" Required="0" Valid="1">
<Description Translatable="1">This setting defines that a 'ITSMChange' object can be linked with 'Ticket' objects using the 'Normal' link type.</Description>
<Group>Framework</Group>
<SubGroup>Core::LinkObject</SubGroup>
<Setting>
<Hash>
<Item Key="Object1">ITSMConfigItem</Item>
<Item Key="Object2">ITSMChange</Item>
<Item Key="Type">Normal</Item>
</Hash>
</Setting>
</ConfigItem>
<!-- EBE -->
- To enable it in sysconfig > Core::LinkObject - Framework (two new boxes)
Actually quite easy..
Now for the next challenge - how do I make it possible to link (preferably mandatory) from a new Ticket to an existing CI ?
Regards
/Eivind
PS - thanks a lot to Lorenzo - it was his answer that got me in the right direction
PPS - how do I make this change survive future upgrades of the ITSM ?