> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pipeshub.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira Data Center Toolset

> Issue tracking and project management integration for AI agents on self-hosted Jira

<div className="max-w-2xl mx-auto mt-12">
  <div className="p-6 border border-gray-200 dark:border-gray-700 rounded-lg bg-blue-50 dark:bg-gray-800">
    <div className="flex items-center mb-4">
      <img src="https://mintcdn.com/pipeshub/8k-iBPRh1yJZHQe1/logo/jira.png?fit=max&auto=format&n=8k-iBPRh1yJZHQe1&q=85&s=4c85f433a48529979a9483588af17bfc" alt="Jira Logo" className="w-8 h-8 mr-3 object-contain flex-shrink-0" width="567" height="567" data-path="logo/jira.png" />

      <h2 className="text-2xl font-semibold m-0">Jira Data Center Toolset</h2>
    </div>

    <p className="text-lg text-gray-700 dark:text-gray-300 mb-4">Issue tracking and project management on self-hosted Jira</p>

    <div className="flex items-center gap-2">
      <span className="px-3 py-1 bg-green-100 dark:bg-green-900 text-green-800 dark:text-green-200 rounded-full text-sm font-medium">
        Ready
      </span>

      <span className="px-3 py-1 bg-purple-100 dark:bg-purple-900 text-purple-800 dark:text-purple-200 rounded-full text-sm font-medium">
        Atlassian
      </span>
    </div>
  </div>
</div>

## Overview

The Jira Data Center toolset lets AI agents work with the Jira you run on your own servers. Agents can create issues, search tickets, add comments, update issues, and more. Use it to automate project management work and to bring Jira into a conversation with an agent.

<Info>
  If Atlassian hosts your Jira for you, that is Jira Cloud. Use the [Jira Cloud toolset](/toolsets/jira/jira) instead. The two toolsets are not interchangeable.
</Info>

### Key Capabilities

* **Create and manage issues** - Create tickets, update them, move them to a new status
* **Search with JQL** - Find issues using Jira Query Language
* **Discover required fields** - Ask Jira which fields a project needs before creating an issue
* **Comment management** - Add and read comments on issues
* **Project operations** - List projects, read project metadata
* **User operations** - Search users, get the current user

***

## Available Tools

| Tool                      | Description                                                                       | Type    |
| ------------------------- | --------------------------------------------------------------------------------- | ------- |
| `get_create_issue_fields` | Get every field a project and issue type needs, with field IDs and allowed values | Search  |
| `create_issue`            | Create a new issue                                                                | Action  |
| `update_issue`            | Update an issue (summary, description, assignee, status, and more)                | Action  |
| `get_issue`               | Get details of a specific issue                                                   | Search  |
| `search_issues`           | Search issues using JQL                                                           | Search  |
| `add_comment`             | Add a comment to an issue                                                         | Action  |
| `get_comments`            | Get comments on an issue                                                          | Search  |
| `get_projects`            | Get all projects you can see                                                      | Search  |
| `get_project`             | Get details of a specific project                                                 | Search  |
| `get_project_metadata`    | Get project metadata (issue types, components)                                    | Search  |
| `search_users`            | Search users by name or email                                                     | Search  |
| `get_current_user`        | Get the signed-in user's details                                                  | Search  |
| `validate_connection`     | Check the Jira connection and show diagnostics                                    | Utility |

***

## Configuration Guide

The Jira Data Center toolset supports **two ways to sign in**: Personal Access Token (PAT) and Basic Authentication.

In both cases the work is split between an admin and each user:

* **The admin** sets up the shared instance under **Workspace Settings → Actions** and enters only the **Base URL**.
* **Each user** then opens **Your actions** and enters their own credentials.

Every user who wants to use the toolset needs their own credentials, because each agent action runs as that user in Jira.

<Warning>
  **This toolset supports Personal Access Token and Basic Authentication only.** OAuth apps you create in the Atlassian Developer Console are for Jira Cloud and will not work here.
</Warning>

| Method                          | Best for                                                                                                                                   |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Personal Access Token (PAT)** | Recommended. Needs Jira Core 8.14 or later. Each user creates their own token and can revoke it at any time.                               |
| **Basic Authentication**        | Older instances that do not support tokens, or where an admin has turned token creation off. Each user enters their username and password. |

<Tabs>
  <Tab title="Personal Access Token">
    #### Step 1: Each user creates a Personal Access Token

    Every user who will use the toolset needs their own token.

    1. Sign in to your Jira.
    2. Click your **profile picture** in the top right, then select **Profile**.
    3. Open the **Personal Access Tokens** tab and click **Create token**.
    4. Give it a name you will recognise, such as `PipesHub Jira Toolset`, set an expiry if you want, then click **Create**.

    <div className="text-center">
      <img src="https://mintcdn.com/pipeshub/uuLTAPtR53lSTg2o/images/toolsets/jira-data-center/pat_create_token.png?fit=max&auto=format&n=uuLTAPtR53lSTg2o&q=85&s=b36d12dfb931dcdaffaf8ababb5c74f7" alt="Create a Personal Access Token in Jira Data Center" className="block mx-auto w-11/12" width="1908" height="937" data-path="images/toolsets/jira-data-center/pat_create_token.png" />
    </div>

    5. Jira shows the token **once**. Copy it and store it somewhere safe.

    <div className="text-center">
      <img src="https://mintcdn.com/pipeshub/uuLTAPtR53lSTg2o/images/toolsets/jira-data-center/pat_copy_token.png?fit=max&auto=format&n=uuLTAPtR53lSTg2o&q=85&s=6491c6e2968cf93388af86dab7c53985" alt="Copy the Personal Access Token — shown once" className="block mx-auto w-11/12" width="1907" height="923" data-path="images/toolsets/jira-data-center/pat_copy_token.png" />
    </div>

    <Warning>
      The token is shown only once. If you close the dialog before copying it, revoke it and create a new one.
    </Warning>

    <Info>
      A token has the same access as the person who created it. An agent using your token can only do what you can do in Jira.
    </Info>

    #### Step 2: Admin — create the instance in Actions

    The admin sets only the Base URL here. No credentials are entered at this step.

    1. In PipesHub, go to **Workspace Settings** → **Actions**.
    2. Find **Jira Data Center** and click **+ Setup** for a new instance.
    3. Choose **Personal Access Token** as the sign-in method, then enter:
       * **Instance Name** (e.g., `Jira Production`)
       * **Base URL** — the root URL of your Jira, such as `https://jira.company.com`, with no trailing slash
    4. Click **Create**.

    <div className="text-center">
      <img src="https://mintcdn.com/pipeshub/uuLTAPtR53lSTg2o/images/toolsets/jira-data-center/actions_admin_setup.png?fit=max&auto=format&n=uuLTAPtR53lSTg2o&q=85&s=ac273f84e94549a32df057dc1738606d" alt="Admin Actions dialog — Instance Name and Base URL only" className="block mx-auto w-11/12" width="1908" height="932" data-path="images/toolsets/jira-data-center/actions_admin_setup.png" />
    </div>

    <Info>
      Opening the instance settings later brings this dialog back, where you can change the **Instance Name** and **Base URL**. A button below it opens **Your actions** so each user can add their own credentials.
    </Info>

    #### Step 3: Each user — add their token in Your actions

    Every user who wants to use the toolset does this with their own token.

    1. In PipesHub, open **Your actions** (under **Personal** in the sidebar).
    2. Find the Jira Data Center instance and open it.
    3. Enter your **Personal Access Token** from Step 1.
    4. Click **Save credentials**.

    <div className="text-center">
      <img src="https://mintcdn.com/pipeshub/uuLTAPtR53lSTg2o/images/toolsets/jira-data-center/your_actions_credentials.png?fit=max&auto=format&n=uuLTAPtR53lSTg2o&q=85&s=8e5ea2c08fdaef1657e7099ebde9b986" alt="Your actions — enter your Personal Access Token" className="block mx-auto w-11/12" width="1897" height="932" data-path="images/toolsets/jira-data-center/your_actions_credentials.png" />
    </div>

    The tile in **Your actions** now shows **Authenticated**. The toolset is connected for you only. Every other user has to repeat this step with their own token.

    #### Step 4: Add the toolset to an agent

    1. Go to the **Home** page.
    2. Next to **Agents**, click **+** to create a new agent.
    3. Name the agent, drag the **Jira Data Center** toolset onto the canvas, connect it to the **Agent Core** node along with your model and chat input and output, then create the agent.

    <div className="text-center">
      <img src="https://mintcdn.com/pipeshub/uuLTAPtR53lSTg2o/images/toolsets/jira-data-center/create_agent.png?fit=max&auto=format&n=uuLTAPtR53lSTg2o&q=85&s=fc419668eaf461876381c84a03aa7733" alt="Agent builder with the Jira Data Center toolset connected" className="block mx-auto w-11/12" width="1917" height="941" data-path="images/toolsets/jira-data-center/create_agent.png" />
    </div>
  </Tab>

  <Tab title="Basic Authentication">
    Use this on instances that do not support Personal Access Tokens, or where an admin has turned off token creation.

    #### Step 1: Admin — create the instance in Actions

    The admin sets only the Base URL here. No credentials are entered at this step.

    1. In PipesHub, go to **Workspace Settings** → **Actions**.
    2. Find **Jira Data Center** and click **+ Setup** for a new instance.
    3. Choose **Basic Authentication** as the sign-in method, then enter:
       * **Instance Name** (e.g., `Jira Production`)
       * **Base URL** — the root URL of your Jira, such as `https://jira.company.com`, with no trailing slash
    4. Click **Create**.

    <div className="text-center">
      <img src="https://mintcdn.com/pipeshub/uuLTAPtR53lSTg2o/images/toolsets/jira-data-center/actions_admin_setup_basic_auth.png?fit=max&auto=format&n=uuLTAPtR53lSTg2o&q=85&s=f685f712f994ee49a2d6cbf19c620f0b" alt="Admin Actions dialog with Basic Authentication — Instance Name and Base URL only" className="block mx-auto w-11/12" width="1901" height="932" data-path="images/toolsets/jira-data-center/actions_admin_setup_basic_auth.png" />
    </div>

    #### Step 2: Each user — add their username and password in Your actions

    Every user who wants to use the toolset does this with their own account.

    1. In PipesHub, open **Your actions** (under **Personal** in the sidebar).
    2. Find the Jira Data Center instance and open it.
    3. Enter:
       * **Username** — your Jira username
       * **Password** — your Jira password
    4. Click **Save credentials**.

    <div className="text-center">
      <img src="https://mintcdn.com/pipeshub/uuLTAPtR53lSTg2o/images/toolsets/jira-data-center/your_actions_credentials_basic_auth.png?fit=max&auto=format&n=uuLTAPtR53lSTg2o&q=85&s=1d99ce9bb10786cbb5eafa094df1b544" alt="Your actions — enter your username and password" className="block mx-auto w-11/12" width="1915" height="937" data-path="images/toolsets/jira-data-center/your_actions_credentials_basic_auth.png" />
    </div>

    <Warning>
      Enter the Jira **username**, not the email address. On many instances these are different.
    </Warning>

    #### Step 3: Add the toolset to an agent

    1. Go to the **Home** page.
    2. Next to **Agents**, click **+** to create a new agent.
    3. Name the agent, drag the **Jira Data Center** toolset onto the canvas, connect it to the **Agent Core** node along with your model and chat input and output, then create the agent.

    <div className="text-center">
      <img src="https://mintcdn.com/pipeshub/uuLTAPtR53lSTg2o/images/toolsets/jira-data-center/create_agent.png?fit=max&auto=format&n=uuLTAPtR53lSTg2o&q=85&s=fc419668eaf461876381c84a03aa7733" alt="Agent builder with the Jira Data Center toolset connected" className="block mx-auto w-11/12" width="1917" height="941" data-path="images/toolsets/jira-data-center/create_agent.png" />
    </div>
  </Tab>
</Tabs>

***

## FAQ

<AccordionGroup>
  <Accordion title="Can I use OAuth with the Jira Data Center toolset?">
    No. This toolset supports **Personal Access Token** and **Basic Authentication** only. OAuth apps created in the Atlassian Developer Console are for Jira Cloud and will not work here.
  </Accordion>

  <Accordion title="Should I use a Personal Access Token or Basic Authentication?">
    |                      | Personal Access Token      | Basic Authentication                            |
    | -------------------- | -------------------------- | ----------------------------------------------- |
    | **Best for**         | Jira Core 8.14 or later    | Older instances, or where tokens are turned off |
    | **Admin sets up**    | Instance Name and Base URL | Instance Name and Base URL                      |
    | **Each user enters** | Their own token            | Their username and password                     |

    Use a **Personal Access Token** unless your instance cannot create them.
  </Accordion>

  <Accordion title="What is the difference between the Jira Data Center connector and toolset?">
    | Aspect        | Connector                                     | Toolset                                     |
    | ------------- | --------------------------------------------- | ------------------------------------------- |
    | **Purpose**   | Sync and index Jira data so you can search it | Let agents do things in Jira                |
    | **Direction** | One way, Jira into PipesHub                   | Two ways, read and write                    |
    | **Use it to** | Search issues, projects, and comments         | Create issues, update tickets, add comments |

    **Example:** use the [connector](/connectors/jira/jira-data-center) to search existing tickets. Use the toolset to let an agent create a new issue or change a ticket's status.
  </Accordion>

  <Accordion title="Why do I have to enter my own credentials?">
    Every agent action runs as a real Jira user. Using your own token means agents can only see and change what you can see and change in Jira, and the history in Jira shows who did it.
  </Accordion>
</AccordionGroup>

***

<Info>
  When searching issues, include a time range, such as "from the last 30 days" or "updated this week". The toolset asks for one so searches stay bounded and results stay accurate.
</Info>

***

## Usage Tips

**How do I create an issue?**\
Ask your agent to "create a Jira ticket" and give it the project key, the title, and the issue type (Task, Bug, or Story). You can also give an assignee, a priority, and labels.

**Why does the agent ask me extra questions before creating an issue?**\
Many projects require custom fields such as Story Points, Sprint, or Due Date. The agent calls `get_create_issue_fields` first to find out what your project needs, then asks you for anything it does not already know. It will not guess a value for a required field.

**How do I search for issues?**\
Ask to "find Jira issues" with the criteria you want. The agent writes the JQL for you. For example: "show me all in-progress issues in project PA from the last week". For your own tickets, just say "my tickets" — the agent uses `currentUser()` and does not need to look you up first.

**How do I assign issues?**\
You can assign by name or email, such as "assign to John Smith". The agent looks up the matching Jira username for you. Data Center identifies people by username, not by account ID.

**How do I update issue status?**\
Ask to "move issue PA-123 to In Progress" or "mark PA-456 as Done". The agent runs the matching workflow transition in Jira.

**What formatting can I use in descriptions and comments?**\
Plain text and Jira wiki markup. Data Center does not use Atlassian Document Format, so there is nothing to convert.