> For the complete documentation index, see [llms.txt](https://docs.silessian.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silessian.com/planapply-for-jira-cloud/global-features/diagram-area/updating-element-details.md).

# Updating element details

Resource details, located on the left side of diagram allows user to update Jira configuration details of imported or new components.

You can also use variable starting with "${atlcloudjira..." to link source and target components. It will provide better description of change for deployment team.

Resource details are using pre-populated select boxes that are fetching data directly from instance. With that, business users don't have to be aware of true resource IDs and just look exactly for configuration items they want. In example below, there is a project searcher used in one of the attributes of Filter resource.

<figure><img src="/files/gggRrk94fHu98qsvqM16" alt="" width="563"><figcaption><p>Resource details view. It contain searchers that helps you find the right components in instance.</p></figcaption></figure>


---

# 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.silessian.com/planapply-for-jira-cloud/global-features/diagram-area/updating-element-details.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.