Jira Integration

The Jira integration lets your company connect Jira Cloud to IntuitivePM. Use it when Jira remains your issue system of record, but you want IntuitivePM tasks, workflows, and agents to read Jira context and coordinate work from the board.

With Jira connected, users can:

• Link Jira issues to IntuitivePM tasks.
• Search and preview Jira issues from IntuitivePM.
• Use Jira issues as Knowledge Sources for agent workflows.
• Let approved agents read Jira issue context through IntuitivePM.
• Review and approve proposed Jira updates before anything is written back to Jira.

How It Works

IntuitivePM connects to Jira through Atlassian OAuth. The Jira token is stored and used by IntuitivePM on the server side. Users and agent runtimes never receive Jira credentials.

When an agent needs Jira context, IntuitivePM reads the selected issue, converts Jira descriptions and comments into safe text, records citations, and gives the agent only the scoped context for its current task or workflow run.

When an agent wants to update Jira, it creates a proposal in IntuitivePM. A human must approve the proposal before IntuitivePM applies it to Jira.

Prerequisites

• A Jira Cloud site.
• Permission in Jira to authorize IntuitivePM for the projects you want to use.
• Company admin access in IntuitivePM.
• Jira enabled for your IntuitivePM company.
• Agent orchestration enabled if you want agents to use Jira issues as workflow context.

Connect Jira

1. Open System -> Integrations -> Integration Hub.
2. Open Jira Cloud.
3. Select Connect Jira.
4. Sign in to Atlassian when prompted.
5. Review and approve the requested permissions.
6. Return to IntuitivePM after the OAuth flow completes.
7. Open the Jira connection details and sync projects.
8. Enable the Jira projects that should be available in IntuitivePM.

After connection, the Jira card shows connection health, connected user, selected projects, last successful check, and any permission or re-authentication warnings.

Admin Diagnostics

Company admins can use the Jira connection details to check whether the integration is healthy before users or agents rely on it.

The diagnostics area shows:

• Connected Jira site and connected account.
• Token and permission health.
• Last successful API call.
• Token expiry and re-authentication warnings.
• Enabled Jira projects.
• Project permission drift summary.
• Whether write-back scopes are present for approved Jira proposals.
• Inbound Jira webhook status and recent event processing results.
• Token refresh and permission/API error history.
• Recent Jira read audit events filtered by action and actor.
• Recent Jira write proposals and proposal audit events.

Use Refresh auth when you want IntuitivePM to validate the current token. Use Re-authenticate when permissions changed in Jira or when IntuitivePM reports that the connection needs attention.

Jira audit defaults are intentionally conservative. Detailed Jira runtime read audit is kept for 180 days by default, and raw webhook payloads are kept for 90 days by default. IntuitivePM automatically applies those defaults in the background: old raw webhook payloads are redacted, and old detailed runtime read audit rows are removed. Your company may have stricter retention settings depending on rollout policy.

Link a Jira Issue to a Task

1. Open a task.
2. Open the Jira Issues section.
3. Select Link Jira issue.
4. Choose the Jira connection.
5. Search by issue key or text.
6. Preview the issue to confirm it is the right one.
7. Link the issue to the task.

The task now shows the Jira issue key, summary, Jira status, last updated time, and a link back to Jira.

When you start an agent workflow from a task, linked Jira issues are included as task context for the workflow. The agent reads them through IntuitivePM, not directly from Jira.

Use Jira as a Knowledge Source

Company admins can also create a Jira Knowledge Source for a specific issue.

1. Open AI Agents -> Knowledge Sources.
2. Select New Source.
3. Choose Jira issue.
4. Select a Jira connection.
5. Search for the issue or enter the issue key.
6. Preview the issue context.
7. Save the source.
8. Attach the source to a workflow node that needs that Jira context.

Use task-linked Jira issues when the issue belongs to one task. Use a Jira Knowledge Source when the issue should be reused in workflow configuration.

Preview Source Resolution

Admins can preview a Knowledge Source before attaching it to a workflow node.

1. Open AI Agents -> Knowledge Sources.
2. Select a Jira Knowledge Source.
3. Use the Connector diagnostics area.
4. Select Preview resolution.

The preview confirms whether the source is ready and shows the safe reference, current status, update time, and configuration hash. It does not expose Jira tokens or other connector credentials.

Audit Source Reads

The same diagnostics area can show recent source activity. Use the audit filters to review reads by action, actor type, source type, and selected Knowledge Source.

This is useful when you need to answer questions such as:

• Did an agent read this Jira issue during a workflow run?
• Which agent read the source?
• Was the read tied to a task or workflow run?
• How much source content was returned?

What Agents Can Read

Agents can receive scoped Jira issue context for the work they are assigned to. The context can include:

• Issue key and summary.
• Status, issue type, priority, labels, and project metadata.
• Sanitized description text.
• Sanitized comment text.
• Linked issue metadata.
• Attachment metadata.
• Citations that show which Jira field or comment supported the answer.

Attachment file contents are controlled separately. If attachment byte access is not enabled for your company, agents can see attachment metadata but cannot read the attachment body.

Jira Write Proposals

Agents cannot directly edit Jira. They can propose changes that a user reviews inside IntuitivePM.

Supported proposal types include:

• Add a Jira comment.
• Move a Jira issue through an allowed transition.
• Update safe fields such as summary, labels, or priority.
• Add a link-back comment from Jira to the IntuitivePM task or workflow run.

To review proposals:

1. Open the IntuitivePM task that is linked to Jira.
2. Open the Jira Issues section.
3. Review the pending proposal.
4. Select Approve or Reject.
5. If approved, select Apply to write the change to Jira.

Before applying a proposal, IntuitivePM checks whether the Jira issue changed after the proposal was created. If Jira changed, the proposal is marked stale and must be reviewed again.

Company admins can also inspect proposal lifecycle audit events from the Jira connection details. The audit view can be filtered by issue key, proposal status, action, and actor type. Use this when you need to confirm who approved, rejected, or applied a proposed Jira write.

Human Approval Steps

Some agent workflows pause at a human approval step before continuing. When a Jira-connected task is waiting for that approval, open the task and expand Agent work.

From the task modal you can:

• Approve the waiting workflow step.
• Request changes with feedback.
• Reject the step when the workflow should stop.

Only users routed to the approval step can make the decision. The task modal shows whether an approval is assigned to you and whether it is overdue. Feedback is required when requesting changes or rejecting a step. Administrators can later filter approval decisions by workflow, task, decision, reviewer, and time window.

Webhooks and Automation

Jira events can also be received through IntuitivePM inbound automation when configured by an administrator. This can be used to create or update IntuitivePM tasks from Jira events, or start an approved workflow when a rule matches.

Webhook automation is optional. You can use Jira search, task links, Knowledge Sources, and write proposals without enabling Jira webhooks.

When Jira webhooks are enabled, company admins can use the Jira connection details to inspect recent inbound events, their processing status, retry count, and any processing error. Use this when a Jira event did not create or update the expected IntuitivePM task.

Security Model

IntuitivePM uses these guardrails for Jira:

• Jira credentials stay on the IntuitivePM server.
• Agent runtimes never receive Jira OAuth tokens.
• Jira reads are scoped to the active company, connection, task, workflow, and lease.
• Jira content is treated as untrusted source data and converted before agents use it.
• Jira writes require human approval.
• Jira issue freshness is checked before approved writes are applied.
• Jira reads, proposals, approvals, rejections, and writes are auditable.

Troubleshooting

Recommended Setup

For most teams:

1. Connect Jira from the Integration Hub.
2. Enable only the projects you want IntuitivePM to use.
3. Link Jira issues to tasks during the pilot phase.
4. Let agents read Jira context and produce citations.
5. Keep Jira write-back in human-approved proposal mode.
6. Enable inbound Jira automation only after the manual link and proposal workflow is understood.

Related Guides

• Integration Hub
• Agent Orchestration
• Assign Work To Agents
• Work Files and Knowledge Sources