Skip to main content
What you can do:
  • Ingest Jira issues into Gradial with full metadata
  • Filter by project, status, issue type, labels, or custom JQL
  • Trigger Gradial execution when tickets match your criteria
  • Write results — previews, links, comments — back to the Jira ticket
  • Sync attachments from Jira into Gradial (Forge OAuth)
Due to Atlassian Forge app limitations, Gradial cannot upload attachments back to Jira when using Forge OAuth. Attachments sync Jira → Gradial only, not in reverse.

​
Prerequisites

Service account requirements:
  • A dedicated Jira account for integrations — not a personal user
  • Must be licensed and discoverable in Jira (so Gradial can assign issues)
  • Must have access to all projects and issues you plan to sync
Required permissions for the service account: Permissions may come from global permissions, project roles, or issue security schemes. See Atlassian OAuth scopes documentation for additional detail.

​
Authentication options

​
Connect Jira to Gradial

Go to Integrations in the Gradial sidebar, find Jira under Ticket System Integrations, and click Connect. Then follow the steps for your authentication method.

​
Option A — Jira Cloud (Email + API Token)

  1. Enter your Jira Base URL (e.g., https://your-company.atlassian.net)
  2. Enter the Email Address of your service account
  3. Generate an API token at https://id.atlassian.com/manage-profile/security/api-tokens
  4. Paste the token into API Token
  5. Click Validate Connection

​
Option B — Jira Cloud (Forge OAuth App)

  1. Select Jira Cloud (Forge OAuth App) as your authentication type
  2. Enter your Jira Base URL and service account Email Address
  3. Enter an API Token to authorize the initial installation
  4. Click Install Forge App and approve the Gradial app in the Jira permissions dialog
  5. Once Forge App Installed is confirmed, click Validate Connection

​
Option C — Jira Server / Data Center (PAT)

  1. Enter your Jira Base URL
  2. Paste the Personal Access Token generated from the service account’s settings
  3. Click Validate Connection

​
Configure routes

Once connected, create routes to define which Jira issues sync into which Gradial workspaces. Jira supports project, issue type, label, and JQL filters. Configure Routes → Optional — Assign Back to Reporter: When enabled, Gradial automatically reassigns a Jira issue back to the original reporter upon completion, so tickets don’t stay assigned to the service account.

​
Troubleshooting

Contact your Gradial Product Specialist if issues persist.