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.If Atlassian hosts your Jira for you, that is Jira Cloud. Use the Jira Cloud toolset instead. The two toolsets are not interchangeable.
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
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.
- Personal Access Token
- Basic Authentication
Step 1: Each user creates a Personal Access Token
Every user who will use the toolset needs their own token.- Sign in to your Jira.
- Click your profile picture in the top right, then select Profile.
- Open the Personal Access Tokens tab and click Create token.
- Give it a name you will recognise, such as
PipesHub Jira Toolset, set an expiry if you want, then click Create.
- Jira shows the token once. Copy it and store it somewhere safe.
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.
Step 2: Admin — create the instance in Actions
The admin sets only the Base URL here. No credentials are entered at this step.- In PipesHub, go to Workspace Settings → Actions.
- Find Jira Data Center and click + Setup for a new instance.
- 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
- Instance Name (e.g.,
- Click Create.
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.
Step 3: Each user — add their token in Your actions
Every user who wants to use the toolset does this with their own token.- In PipesHub, open Your actions (under Personal in the sidebar).
- Find the Jira Data Center instance and open it.
- Enter your Personal Access Token from Step 1.
- Click Save credentials.
Step 4: Add the toolset to an agent
- Go to the Home page.
- Next to Agents, click + to create a new agent.
- 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.
FAQ
Can I use OAuth with the Jira Data Center toolset?
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.
Should I use a Personal Access Token or Basic Authentication?
Should I use a Personal Access Token or Basic Authentication?
Use a Personal Access Token unless your instance cannot create them.
What is the difference between the Jira Data Center connector and toolset?
What is the difference between the Jira Data Center connector and toolset?
Example: use the connector to search existing tickets. Use the toolset to let an agent create a new issue or change a ticket’s status.
Why do I have to enter my own credentials?
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.
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.
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.