Jira

Read issues and post comments from workflows - a session-tracker adapter with multi-field credential dispatch.

Partially implemented. Jira is a session tracker adapter: workflows bound to a Jira project can read an issue (issue.read) and post comments (issue.add_comment), and agent sessions get Jira issue context. There are no Jira issue-creation, update, search, custom-field, or sprint nodes, and issue.update_status returns capability_not_supported for Jira bindings. There is also no inbound Jira webhook ingestion.

The Jira integration lets workflows read Jira issues and post comments, so a Jira-tracked project can drive agent sessions the same way a Linear-tracked one does.

What you can do

Read an issue - issue.read returns the issue in canonical form (key, title, status, description)
Post a comment - issue.add_comment adds a comment to the issue
Agent session context - sessions on Jira-bound projects resolve the issue's key, title, and status
Agent-side Jira access - the multi-field credential is dispatched into worker environments as JIRA_SITE, JIRA_EMAIL, and JIRA_API_TOKEN, so agents can call the Jira REST API directly

What you cannot do (yet)

Create, update, search, or transition issues from workflow nodes
Update issue status - issue.update_status is unsupported on Jira bindings (supportsStatusUpdate: false)
Set custom fields, assignees, watchers, or sprints
Trigger workflows from Jira events - there is no inbound Jira webhook ingestion (a downstream event-router adapter exists, but nothing produces Jira events into it)

Connect Jira

The Jira integration uses a multi-field credential:

Field	Example	Notes
Jira site URL	`https://mycompany.atlassian.net`	Jira Cloud only; do not include a path
Email address	`jane@mycompany.com`	Must match the Jira account that owns the API token
API token	`ATATT3x...`	Generated in Atlassian account settings

Create a Jira API token

Go to atlassian.com/account/profile/personal-security/api-tokens
Click Create API token
Label: e.g., "Rensei"
Click Create and copy the token - it is shown only once

Add the credential to your org

Store the site URL, email, and API token as an org credential with provider type Jira. The tracker adapter resolves the org's Jira credential by provider type at call time.

Bind a Rensei project to Jira

Go to Project Settings → Trackers
Select Jira as the issue tracker
Enter the tracker path for your Jira project, e.g. jira:project:PROJ-1

Once bound, the generic session-tracker nodes (issue.read, issue.add_comment) on workflows in this project route to Jira.

Workflow nodes

Node	Supported on Jira	Description
`issue.read`	Yes	Fetch the issue in canonical form
`issue.add_comment`	Yes	Post a comment on the issue
`issue.update_status`	No	Returns `capability_not_supported` for Jira

Post a comment with agent output:

- id: post_comment
  type: action
  nodeId: issue.add_comment
  config:
    issueId: "{{ $trigger.data.issueId }}"
    body: |
      Agent update:

      {{ steps.agent.output.summary }}

Credential dispatch to agents

Unlike the early integration, Jira's multi-field credential is serialized into the worker credential snapshot. The dispatch adapter maps each field to a conventional env var:

Credential field	Env var in the worker
`site`	`JIRA_SITE`
`email`	`JIRA_EMAIL`
`apiToken`	`JIRA_API_TOKEN`

Agents that need richer Jira operations than the node surface offers (create, transition, JQL search) can call the Jira REST API directly using these variables.

API token rotation

Jira API tokens do not expire by default, but you can revoke and regenerate them:

Go to atlassian.com/account/profile/personal-security/api-tokens
Delete the token you created for Rensei
Create a new token
Update the org's Jira credential with the new token value

Limitations

Read + comment only - no issue CRUD, transition, JQL search, custom-field, or sprint nodes
Jira Server / Data Center - the integration targets Jira Cloud (atlassian.net domains); Jira Server and Data Center are not supported
No inbound webhooks - Jira events cannot trigger workflows; the integration is outbound-only
Permissions - the API token grants the same permissions as your Jira user; reads and comments fail where the user lacks access

Troubleshooting

"Authentication failed"

Verify your Jira site URL is correct (https://mycompany.atlassian.net, not mycompany.jira.com)
Check that your email and API token are correct
Regenerate your API token and update the org credential

"Issue not found"

Verify the issue key is correct (e.g., ENG-123, not ENG 123)
Ensure you have permission to view the issue in Jira

"Agent cannot access Jira"

Confirm a Jira credential exists at the org level
Check the session's environment for JIRA_SITE / JIRA_EMAIL / JIRA_API_TOKEN
Check the session's activity log for credential resolution errors

Next steps

Project trackers - Bind Jira to a Rensei project
Workflow triggers - Use GitHub and Linear events to drive workflows that read/comment on Jira issues
Agent cards - Assign agents to Jira-tracked projects

On this page