Skip to main content
Jira Logo

​
Jira Toolset

Issue tracking, project management, and team collaboration

ReadyAtlassian

​
Overview

The Jira toolset enables AI agents to interact with your Jira workspace. Agents can create issues, search tickets, add comments, update issues, and more. This toolset is ideal for automating project management workflows and integrating Jira into conversational AI experiences.

​
Key Capabilities

  • Create and manage issues - Create new tickets, update existing ones, change status
  • Search with JQL - Find issues using Jira Query Language
  • Comment management - Add and retrieve comments on issues
  • Project operations - List projects, get project metadata
  • User operations - Search users, get current user info

​
Available Tools

​
Configuration Guide

The Jira toolset supports two authentication methods. In both, an admin first configures the shared instance under Workspace Settings → Actions, then each user connects their personal account under Your actions.

​
Step 1: Access the Atlassian Developer Console

  1. Go to developer.atlassian.com/console/myapps/ and sign in with your Atlassian account (must have admin access to your Jira workspace).
Atlassian Developer Console

​
Step 2: Create an OAuth 2.0 integration

  1. Click Create in the top-right corner.
  2. Select OAuth 2.0 integration.
  3. Enter a name (e.g., PipesHub Jira Toolset) and accept the developer terms.
  4. Click Create.
Create OAuth Integration

​
Step 3: Get the Redirect URI from PipesHub

Before configuring the Callback URL in Atlassian, copy the Redirect URI from PipesHub.
  1. In PipesHub, go to Workspace Settings → Actions.
  2. Find Jira in the list and click + Setup for a new instance.
  3. Copy the Redirect URI shown in the dialog.
PipesHub Configure Jira toolset — copy the Redirect URI

​
Step 4: Configure the Callback URL in Atlassian

  1. In Atlassian Developer Console, click Authorization in the left sidebar.
  2. Click Add under OAuth 2.0 (3LO).
  3. Paste the Redirect URI from PipesHub into the Callback URL field.
  4. Click Save changes.
Add Callback URL
The Callback URL must match exactly. Any mismatch — trailing slash, protocol, casing — will cause authentication to fail.

​
Step 5: Add required scopes

  1. In the left sidebar, click Permissions.
  2. Add scopes for both User identity API and Jira API.
User Identity API
User Identity API Scopes
Jira API — Classic scopes
Jira Classic Scopes
Jira API — Granular scopes
Jira Granular Scopes

​
Step 6: Copy Client ID and Client Secret

  1. In the left sidebar, click Settings.
  2. Under Authentication details, copy:
    • Client ID — used as Client ID in PipesHub.
    • Secret — used as Client Secret in PipesHub.
Copy OAuth Credentials

​
Step 7: Admin — configure the toolset in Actions

  1. In PipesHub, return to Workspace Settings → Actions, find Jira, and reopen the setup dialog.
  2. Confirm the Redirect URI matches the Callback URL you saved in Atlassian in Step 4.
  3. Enter:
    • Instance Name (e.g., Jira Production)
    • Client ID — from Step 6
    • Client Secret — from Step 6
    • Atlassian Site URL — your Jira site URL (e.g., https://your-domain.atlassian.net; no trailing slash)
  4. Click Create.
Enter Client ID, Client Secret, and Atlassian Site URL in PipesHub
Atlassian Site URL is an org-level field — it points to the specific Jira Cloud site this toolset instance will act on. Client ID and Client Secret are the org’s OAuth app credentials. Per-user tokens are issued by Atlassian when each user authenticates in the next step.

​
Step 8: Authenticate the toolset

Authentication uses the same OAuth flow in either location:
  • Admins can authenticate the shared instance directly under Workspace Settings → Actions.
  • Users can authenticate their own personal instance under Your actions (in the Personal section of the sidebar).
  1. On the Jira tile (in Actions or Your actions), click Authenticate with OAuth.
  2. A popup opens to Atlassian’s authorization page — select your Jira site from the dropdown.
Select Jira Site
  1. Review the permissions and click Accept.
Accept Permissions
  1. The popup closes and the Jira tile shows Authenticated status.
Authorize using the same email as your PipesHub account. Using a different email causes permission issues on the PipesHub platform.

​
Step 9: Add Jira to an agent

  1. Go to the Home page.
  2. Next to Agents, click + to create a new agent.
  3. Give the agent a name, drag the Jira toolset onto the canvas, connect it to the Agent Core node with your model and chat input/output, then create the agent.
Agent builder with Jira toolset connected

​
FAQ

Choose OAuth for the simplest per-user experience. Choose API Token when you cannot register an Atlassian OAuth app or when each user wants to manage their own token (for example, to set tighter scopes or expiry).
Example: Use Jira Connector to search and retrieve existing ticket information. Use Jira Toolset to let agents create new issues or update ticket status.
When searching issues, always include a time range (e.g., “from the last 30 days” or “updated this week”) to get accurate results.

​
Usage Tips

How do I create an issue?
Simply ask your agent to “create a Jira ticket” and provide the project key, title, and issue type (Task, Bug, or Story). You can also specify assignee, priority, and labels. How do I search for issues?
Ask to “find Jira issues” with specific criteria. The agent will use JQL syntax automatically. For example: “show me all in-progress issues in project PA from the last week” How do I assign issues?
You can assign by name (e.g., “assign to John Smith”) or by email. The agent will look up the correct account ID automatically. How do I update issue status?
Ask to “move issue PA-123 to In Progress” or “mark PA-456 as Done”. Common statuses include “To Do”, “In Progress”, and “Done”.