> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.4-changes-overview/improvements-to-linking-work-items.md).

# Improvements to Linking Work Items

## Copying communications of related work items when creating a new linked work item

We've made an enhancement to the sharing of communications when [creating new linked work items direct from Cases / Tickets](https://docs.enate.net/enate-help/work-manager/work-manager-2021.1/working-with-linked-work-items/creating-new-linked-work-items). Now, when you choose to share communications between linked work items, the communications from *related* work items are also shared with the new work item. 

For example, when creating a new linked Case/Ticket, you can copy work item communications i.e. emails (including email attachments) and notes from the original Case/Ticket to the new linked Case. In this scenario, communications in the launching Case's Actions will now also be copied. Similarly, a split Ticket will now copy across communications from its Parent Ticket.

You can find out more about related vs linked work items [here](https://docs.enate.net/enate-help/work-manager/work-manager-2021.1/working-with-linked-work-items/related-group-vs-linked-work-items).

## Improvements to Viewing Linked Work Items

We have also made improvements to the existing 'Linked Work Item functionality'. Now when a work item is linked to another but is then subsequently merged, split or converted into a Case, the work items resulting from this will retain a link to the other. Previously this link was not persisted in such scenarios.

For example:

* When a Ticket is linked to another work item and that Ticket is merged with another, the merged Ticket will also have a link to the other work item.
* When a Ticket is linked to another work item and that Ticket is split into multiple Tickets, the subsequent child Tickets will also have a link to the other work item.
* When a Ticket is linked to another work item and that Ticket is later converted into a Case, the subsequent Case will also have a link to the other work item.

{% hint style="info" %}
Note that when merging an Action with another work item into a child item, because Actions cannot be linked, it is the Action's parent Case that will be linked to the child item.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.4-changes-overview/improvements-to-linking-work-items.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.