- 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)
- Read attached Jira Cloud Forms and their answers as part of the issue’s context
- Inspect Jira Cloud automation rules and templates, approve changes to a rule’s project scope or enabled state, and create disabled rules from templates where available
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
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 Settings → Integrations, find Jira under Ticket System Integrations, and add a connection. Then follow the steps for your authentication method.Option A — Jira Cloud (Email + API Token)
- Enter your Jira Base URL (e.g.,
https://your-company.atlassian.net) - Enter the Email Address of your service account
- Generate an API token at
https://id.atlassian.com/manage-profile/security/api-tokens - Paste the token into API Token
- Click Validate Connection
Option B — Jira Cloud (Forge OAuth App)
- Select Jira Cloud (Forge OAuth App) as your authentication type
- Enter your Jira Base URL and service account Email Address
- Enter an API Token to authorize the initial installation
- Click Install Forge App and approve the Gradial app in the Jira permissions dialog
- Once Forge App Installed is confirmed, click Validate Connection
Option C — Jira Server / Data Center (PAT)
- Enter your Jira Base URL
- Paste the Personal Access Token generated from the service account’s settings
- 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. In webhook mode, a matching filter alone does not start work. A recognized Gradial mention or assignment trigger must also apply. For Jira Cloud, a webhook route can use JQL to narrow triggered issues; a JQL-filtered route must be the only enabled route for that project within the integration. Avoid overlapping integrations for the same issues, which can create duplicate Gradial Tasks. 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.Read Jira Forms
For Jira Cloud issues, Gradial can read attached Forms, also known as ProForma forms, including their simplified answers. Ask Gradial to read the forms on a specific issue when the brief lives in a form rather than the issue description. Available form answers also become part of the issue’s imported context. The connected account needs access to the issue and its forms. If the Forms API is unavailable, the ordinary issue can still load without the form answers; that does not mean the issue has no forms. Ask Gradial to read the forms explicitly to identify the access problem. This capability reads attached forms. It does not create or edit forms and is not available for Jira Server / Data Center.Manage Jira Cloud automation rules
Automation management requires a Jira Cloud — Email + API Token connection and the Jira permissions needed for the requested rule and projects. Forge OAuth and Jira Server / Data Center connections do not support this capability. A successful ordinary Jira connection test does not establish automation access; ask Gradial to check automation capabilities first. Gradial can list rules, inspect their state and project scopes, and discover Atlassian templates and their required parameters. A board is a view over issues, so identify the underlying Jira projects before asking to change a rule’s scope.Change a rule’s scope or state
- Ask Gradial to inspect the rule and prepare the exact change, such as adding a project to its scope or disabling it.
- Review the current and proposed projects or state, including any warning and any projects being removed.
- Approve the specific change in Gradial. Gradial checks that the rule has not changed since the plan, applies the approved change, and reads it back.
Create a disabled rule from a template
Access: Template-based rule creation must be enabled for your organization. Contact your Gradial team to get access.- Ask Gradial to find an Atlassian template and confirm one target Jira project.
- Provide the template’s required parameter values. Gradial prepares a plan showing the template, project, parameters, and disabled state.
- Approve creation in Gradial. The resulting rule is disabled so you can review it before it runs.
- Request a separate plan and approval when you want to enable the rule.
Reporting on your Jira data
With Jira connected, you can ask Grady to build a dynamic artifact that reports against it — what’s open, what’s blocked, and what’s been waiting longest, grouped however your team works — without exporting to a spreadsheet or waiting on someone to build a Jira view. Because the app queries the connected system on refresh, it reflects the current state of Jira rather than a snapshot.Troubleshooting
Contact your Gradial Product Specialist if issues persist.