- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2024 01:11 PM
I have this incident where I created a child(from its related list),
But the new Incident created using this related list is populated in the Parent field,
In the Related list condition, it is showing (Child=INC0052616), but I created the child incident from this Incident (INC0052616). Then, I opened the related list in the new window.
Now, I am at the Task Relationship table, I opened the record,
I don't understand the relationship as I created the child from the Incident Record (INC0052616) so shouldn't it be populated in the Parent field and INC0052655 in the Child field? And if you can explain the Type Contains::Task of, that will be very helpful.
Thanks,
Muhammad Hamza
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2024 01:27 PM - edited 04-30-2024 01:28 PM
Parent/Child are bad names for these fields, but what this is basically saying is that your new incident contains a task of the old incident. Essentially that it is a task of the first incident.
This is always a little hard to explain. The Parent and Child are not intuitive if you're dealing with the task relationship table, the relatonship between the two fields (parent/child) is defined by the relationship type itself. Honestly, if you're just dealing with other incidents it's much easier to use the Incident related table, which will use the Parent field on the incident for itself and be much less confusing.
Edit: To answer the other part of your question, that table is used to define relatonships between any record that has extended task to any other record that has extended task. I've seen it used primarily for CMDB or other complex data models in the system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2024 01:27 PM - edited 04-30-2024 01:28 PM
Parent/Child are bad names for these fields, but what this is basically saying is that your new incident contains a task of the old incident. Essentially that it is a task of the first incident.
This is always a little hard to explain. The Parent and Child are not intuitive if you're dealing with the task relationship table, the relatonship between the two fields (parent/child) is defined by the relationship type itself. Honestly, if you're just dealing with other incidents it's much easier to use the Incident related table, which will use the Parent field on the incident for itself and be much less confusing.
Edit: To answer the other part of your question, that table is used to define relatonships between any record that has extended task to any other record that has extended task. I've seen it used primarily for CMDB or other complex data models in the system.