> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/da/knowledge-base/knowledge-base-articles/entry-settings/jira.md).

# Jira

Konfigurer dashboardposter til Jira i Remote Desktop Manager, herunder URI’en til sagsstyringsserveren, e-mail, API-token, projektnøgle, sidestørrelse og sagsfilter.

Denne artikel beskriver de mange indstillinger og valgmuligheder, der er tilgængelige for sessionsposter ***Jira*** i Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>INDSTILLINGER</strong></td><td><strong>BESKRIVELSE</strong></td></tr><tr><td><strong>Navn</strong></td><td>Navnet på posten.</td></tr><tr><td><strong>Mappe</strong></td><td>Den mappe, hvor posten findes.</td></tr><tr><td><strong>Visning</strong></td><td><p>Hvordan posten åbnes:</p><ul><li><strong>Integreret (faner)</strong> — Åbner posten i en fane i hovedvinduet.</li><li><strong>Fradocket</strong> — Åbner posten i et separat vindue. Yderligere lister lader Dem vælge skærmen og det virtuelle skrivebord, hvor vinduet åbnes.</li></ul><p>På Linux indeholder listen også <em><strong>Standard (nedarvet)</strong></em>, som bruger visningstilstanden for den nærmeste overordnede mappe, der angiver en, og ellers standarden for posttypen. Den tilstand, den opløses til, vises ved siden af listen.</p></td></tr><tr><td><strong>Legitimationsoplysninger</strong></td><td>Kilden til de legitimationsoplysninger, posten bruger.</td></tr></tbody></table>

<table><thead><tr><th width="220">INDSTILLINGER</th><th>BESKRIVELSE</th></tr></thead><tbody><tr><td><strong>URI til sagsstyringsserver</strong></td><td>Angiv URL’en til Deres Jira-instans. En gyldig HTTP- eller HTTPS-URL er obligatorisk. Klik på knappen <em><strong>Naviger URL</strong></em> for at åbne URL’en i Deres webbrowser.</td></tr><tr><td><strong>Mail</strong></td><td>Angiv e-mailadressen til Jira-kontoen. En e-mailadresse er obligatorisk.</td></tr><tr><td><strong>API-token</strong></td><td>Angiv API-tokenet til Jira-kontoen. Et API-token er obligatorisk.</td></tr><tr><td><strong>Projektnøgle</strong></td><td>Angiv nøglen til det Jira-projekt, som dashboardet som standard viser sager fra.</td></tr><tr><td><strong>Sidestørrelse</strong></td><td>Angiv det maksimale antal sager, der hentes ved hver opdatering, fra 50 til 100 i trin på 25. Standarden er 50.</td></tr><tr><td><strong>Tildelt til mig</strong></td><td>Vis kun de sager, der er tildelt Jira-kontoen. Ryd denne valgmulighed for at vise alle åbne sager i omfanget. Denne valgmulighed er markeret som standard.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/da/knowledge-base/knowledge-base-articles/entry-settings/jira.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.