# Storing the Counterpart Link in the Task Comment
When managing tasks across different platforms or systems, it's essential to maintain clear links between related items. In this article, we’ll explore how to associate tasks in your workspace with their counterparts using Getint. You can improve your workflow by storing counterpart references as comments in both tickets and tasks.
{% hint style="info" %}
Note: If you would like to bulk filter or change tasks on your workspace(s) through their counterpart’s ID / URL more efficiently, please refer to [Storing reference ID / URL of counterpart](https://docs.getint.io/getintio-platform/workflows/storing-reference-ids-urls-across-integrations).
{% endhint %}
### How to Link Comments
* Go to your integration and add or edit a type mapping to bring up the **type mapping configuration:**
We will use a Jira - Azure integration as an example
* Go to the **Comments & Attachments tab**, and mark the **Automatically link comments to related items when created** checkbox.
* After ticking the checkbox, click **Apply** at the bottom right of the **type mapping configuration** window, and save the changes made to your integration. From now on, this effect will apply to all of your new synchronized comments. Remember that if you want this feature to be available for all tasks, you need to enable the setting for all type mappings.
{% hint style="info" %}
This checkbox is disabled by default to avoid confusion from mass notifications when the tickets/tasks are updated with comments after synchronization or migration, especially in large-scale operations.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.getint.io/getintio-platform/workflows/storing-the-counterpart-link-in-the-task-comment.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.