# Linking objects

Each component contain two handlers:

* Source - it's a starting place or arrow indicating a relation of two components
* Target - it's a destination place of components' relation

### Linking objects on diagram

Linking objects is a subject of validation. Validation is based on possible connections that makes sense and are achievable in Jira configuration.

Below there is an example of possible and invalid connection. 

> *It is reasonable to connect custom field (it's attributes like name or ID) inside Filter e.g. insdie used JQL.*\
> *However it doesn't make sense or bring any value, to embed custom field attributes inside attributes of issue type.*

<figure><img src="/files/ck6M6u4yget1m4zlz4SZ" alt=""><figcaption><p>Invalid connection.</p></figcaption></figure>

<figure><img src="/files/AA98xP6vO2rRkFHVH94P" alt=""><figcaption><p>Possible connection.</p></figcaption></figure>

### Linking objects inside attributes

Linking objects on diagram, doesn't fully explains the realation between two components. To provide more details, you can optionally embed variables inside target compone. wut details.&#x20;

1. During a linking process, you will see similar popup message.
2. Click on desired attribute of source component. It will copy to clipboard a variable indicating source attribute value.
3. Paste value inside chosen attribute of linked target component

<figure><img src="/files/zODpZiEPsP9JVrUJfjXh" alt=""><figcaption><p>Copy source attribute variable into clipboard.</p></figcaption></figure>

4. Paste copied value inside chosen attribute of target component. The example linked attribute value will look like this:

JQL attribute:

```
${atlcloudjira_customfield.MyNewCustomField.id} = "Some value" and project = ABC ORDER BY Rank ASC
```

<figure><img src="/files/k6fQAYlKBKJNO9yJyfgc" alt=""><figcaption><p>Now properties of source and target components are linked with variable</p></figcaption></figure>

5. Update component and save plan. Deployment team will now know exactly what was your true intention behind linking of two components.


---

# 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.silessian.com/planapply-for-jira-cloud/global-features/diagram-area/linking-objects.md?ask=<question>
```

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.