Documentation

Jira

Read and write Jira tickets (Cloud or Server/Data Center) from a pipeline, in BYO mode.

Jira

The Jira integration connects your issue tracker to your pipelines: to read project status (tickets, sprints, transitions) and to act (create a ticket, move it forward, comment). It works with both Jira Cloud and Jira Server / Data Center.

What you can do with it

  • Search tickets (JQL), read a ticket, list projects and the available transitions.
  • Create a ticket, transition it from one status to another, add a comment.
  • Feed an agent that summarizes a project's progress or automatically opens a ticket from an inbound signal (email, form, alert).

Tools and nodes

  • Read tools (made available to an agent): jira.search, jira.get_issue, jira.list_projects, jira.list_transitions.
  • Write tools (with confirmation): jira.create_issue, jira.transition_issue, jira.add_comment.
  • jira_report node — deterministic read of a set of tickets, published into the context.
  • jira_create_issue node — ticket creation on output, with an exactly-once guarantee (no duplicate on retry).

Connection (BYO)

  1. Administration → Integrations → Jira.
  2. Choose the mode:
    • Jira Cloud — email + API token (Basic authentication, /rest/api/3 API).
    • Jira Server / Data Center — personal token (Bearer authentication, /rest/api/2 API).
  3. The host is locked to https and ticket/project keys are validated (anti-SSRF protection). Credentials are encrypted at rest and scoped to your organization.

Jira is a strict BYO connector: no metering, no betool margin. You use your own instance and your own Jira permissions.

Use cases

  • Support → ticket — an inbound email qualified by an agent automatically creates a Jira ticket in the right project.
  • Progress report — every morning, a pipeline reads the open tickets and sends a readable status update to the team.