I would like to implement Ticket to Ticket relations (lnkTicketToTicket) so I will be able to do any n-n relation between changes, requests, incidents and problems.
Althoguh is not difficult (I made it before for iTop1.2) I'm asking why is not implemented this way on the out-of-box datamodel as it would be simple and flexible allowing any type of ticket relation instead of creating different attributes for each kind of Ticket.
My question is: Once I implemented this how can I remove the existing relations from the datamodel (this is for example related_request_list, related_incident_list, related_problems_list in Change object).
.. and when removed I understand that the toolkit won't remove the fields from database, but fresh resinstallation will create them?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to implement Ticket to Ticket relations (lnkTicketToTicket) so I will be able to do any n-n relation between changes, requests, incidents and problems.
Althoguh is not difficult (I made it before for iTop1.2) I'm asking why is not implemented this way on the out-of-box datamodel as it would be simple and flexible allowing any type of ticket relation instead of creating different attributes for each kind of Ticket.
My question is: Once I implemented this how can I remove the existing relations from the datamodel (this is for example related_request_list, related_incident_list, related_problems_list in Change object).
.. and when removed I understand that the toolkit won't remove the fields from database, but fresh resinstallation will create them?
Thanks