---
title: "Jira Data Center: Integration für KI-Agenten | Langdock"
description: "Verbinde Jira Data Center mit Langdock. Agenten und Workflows nutzen 24 Actions, zum Beispiel „Add comment“ und „Create issue“."
url: "https://langdock.com/de/integrations/jira-data-center"
language: "de"
---

[Integrationen](https://langdock.com/de/products/integrations)

# Jira Data Center: Integration für KI-Agenten

Track and manage issues, projects, and releases

Verbinde Jira Data Center mit Langdock und nutze es im Chat, in Agenten und in Workflows.

24 Actions · 2 Triggers

[Kostenlos testen](https://app.langdock.com/signup) [Mit Sales sprechen](https://langdock.com/de/talk-to-sales)

Beschreibungen, Actions und Beispiel-Prompts kommen direkt aus dem Produkt und sind dort auf Englisch verfasst.

## Actions für Jira Data Center

Jede Action ist ein Schritt, den ein Agent oder Workflow in Jira Data Center ausführen kann.

- Add comment

  Adds a comment to an issue. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
- Create issue

  Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask.
- Create subtask · Creates a subtask for an existing issue.
- Create version

  Creates a new release version in a Jira project (e.g., 'RELEASE - 1.1.0'). Use this as the first step in a release workflow: create the version, then bulk-update ticket fixVersions to it, then transition tickets to 'Released'. Requires Administer Projects permission.
- Find components

  Returns a paginated list of components for one or more projects. Use this to discover component IDs before creating or updating issues with components.
- Find users · Returns a list of active users that match the search string and property.
- Get all issue types for user · Gets all issue types for a user.
- Get comments

  Returns all comments for an issue. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
- Get current user · Gets details about the user of the current connection.
- Get custom field options

  Returns allowed options for a given custom field, scoped to the create metadata of a project and issue type.
- Get field metadata for issue type · Gets all available field metadata for an issue type.
- Get fields

  Returns all Jira fields with schema metadata. Use this to find field IDs (e.g., customfield_12345) and understand their types.
- Get issue · Gets an issue by id or key.
- Get issue types for project · Gets all issue types for a project.
- Get priorities

  Returns all issue priorities (id and name). Use this to map human-friendly names to IDs.
- Get project · Returns the project details for a project.
- Get project stages · Gets the stages for issue types of a project.
- Get recent projects

  Returns a list of up to 20 projects recently viewed by the user that are still visible to the user.
- Get transition ID · Gets available transition ids for a Jira issue.
- Get versions

  Lists all release versions for a Jira project. Use this to look up version IDs before creating issues, updating fixVersions on tickets, or building release workflows. Supports filtering by status (released, unreleased, archived).
- Move issue by transition ID · Moves an issue through workflow stages using a transition id.
- Search for issues · Searches for issues using JQL.
- Update comment

  Updates a comment. Call the search_for_issues action to get the issue ID or key if the user just provides the issue name.
- Update issue

  Updates fields on an existing Jira issue such as summary, description, assignee, priority, labels, due date, components, fix versions, or custom fields.

## Trigger für Jira Data Center

Ein Trigger startet einen Workflow, sobald in Jira Data Center etwas passiert.

- New issue · Triggers when new issues are created. Optionally filter with JQL.
- Updated issue

  Triggers when an existing Jira issue is modified (e.g., status change, field edit, reassignment). Does not fire for newly created issues — use "New issue" for that.

## Einrichtung und Berechtigungen

Eine Action kann nach deiner Bestätigung fragen, bevor sie ausgeführt wird. In einem Agenten steht jede Action auf „Immer erlauben“ oder „Braucht Bestätigung“.

### Dokumentation

- [Integrationen nutzen](https://docs.langdock.com/de/using-langdock/guides/integrations/using-integrations)
- [So funktionieren Verbindungen](https://docs.langdock.com/de/using-langdock/integrations/connections)
- [Zugriff auf Actions verwalten](https://docs.langdock.com/de/admin/manage-integrations/manage-action-access)

[Alle Integrationen](https://langdock.com/de/products/integrations)
