How to connect Change task to RITM

[Eric K3]

I have a catalog item which is a service process that one of our internal groups performs for other org groups. There are 4 tasks, which I made Change tasks because they are actually performing changes on both test and prod systems. Two of these tasks require confirmation/verification on the part of the requester before the task can be closed, so the next workflow activity and task can be created and assigned.

The way I thought about doing this as simple as possible is to have the tech work the change task and keep the state in either work-in-progress or pending and add notes to the parent RITM asking the requester to confirm/verify the changes and reply back with success. The reply would come back through the RITM to the assignment group, who would then mark the change task as closed.

Question is: How do I connect or associate the RITM to the Change task so that it is easy for the techs working the Change tasks to quickly and easily go to the RITM to add their comments for the requester?

This is the Change Task form:

[Abhinay Erra]

I am sorry, you will also need to create a relationship for this as shown in the screenshots. Click on the Relationships module and create a new relationship as shown below

Then go to the change_task form and configure->Related lists and this new related list on to the form

[jbauguess]

I have a slightly unorthodox solution, but perhaps try using Task Relationships and the task_rel_task table.   There's a few graphics of how the tasks appear when you add the Task Relations field to your form.

This way the change tasks can be associated with the change (as the parent) and with the request item (through a relationship).

We recently started using this for relating incidents/changes/problems/request items.   The things like change task, catalog task, problem task are still related directly in a 1:M relationship with their parent record.   But theoretically, we could relate a change task to a request item or incident this way without disturbing the change task > change relationship and without adding a custom field.