Jira Cloud (Software)

Technical Preview

Overview

A client-mode connector for a curated DevOps / OT slice of the Jira Cloud platform REST API v3 under https://YOUR_SITE.atlassian.net:

Catalog connector event	Entity / path	Notes
(smoke)	`GET /rest/api/3/myself`	Authenticated user
(discovery)	`GET /rest/api/3/project`	List projects
POST issue (from alarm)	`POST /rest/api/3/issue`	Requires `fields.project`, `fields.issuetype`, `fields.summary`
POST issue/{key}/transitions	`POST /rest/api/3/issue/{issueIdOrKey}/transitions`	Requires `transition.id`
GET search?jql=	`GET /rest/api/3/search/jql`	Enhanced search — legacy `/rest/api/3/search` is removed (410)

BASE_ADDRESS is https://{site}.atlassian.net (no trailing slash; endpoints already include /rest/api/3/...). Topics use devops/jira-cloud/<object>/<verb>.

Use /rest/api/3/search/jql, not /rest/api/3/search. Request fields explicitly (default returns IDs only). Paginate with nextPageToken. JQL must be bounded.

Catalog also mentions a server webhook for issue events. This package ships client events only. Register Atlassian webhooks via admin UI or Webhooks REST; inbound receive would need a separate ENABLE_SERVER connector.

Prefer Hub secrets for tokens and passwords. This template has not been verified against a live Atlassian site. Status remains blocked until an authenticated live smoke succeeds.

Basic Syntax

# Coreflux REST_API template — Jira Cloud (Software) curated slice
# Auth: Bearer {value.json.access_token} (OAuth 3LO) or Basic email + API token via config
# BASE_ADDRESS: https://YOUR_SITE.atlassian.net

DEFINE ROUTE JiraCloudRestApi WITH TYPE REST_API
    ADD REST_API_CONFIG
        WITH BASE_ADDRESS "https://YOUR_SITE.atlassian.net"
        WITH ENABLE_CLIENT "true"
        WITH USE_SSL "true"
        WITH REQUEST_TIMEOUT '60'
        WITH DEFAULT_CONTENT_TYPE "application/json"
    ADD EVENT Getmyself
        WITH SOURCE_TOPIC "devops/jira-cloud/myself/get"
        WITH DESTINATION_TOPIC "devops/jira-cloud/myself/get/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/rest/api/3/myself"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"
    ADD EVENT Listprojects
        WITH SOURCE_TOPIC "devops/jira-cloud/project/list"
        WITH DESTINATION_TOPIC "devops/jira-cloud/project/list/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/rest/api/3/project"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"
    ADD EVENT Createissue
        WITH SOURCE_TOPIC "devops/jira-cloud/issue/create"
        WITH DESTINATION_TOPIC "devops/jira-cloud/issue/create/response"
        WITH METHOD "POST"
        WITH ENDPOINT "/rest/api/3/issue"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Content-Type" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"
        WITH BODY "{payload}"
    ADD EVENT Transitionissue
        WITH SOURCE_TOPIC "devops/jira-cloud/issue/transition"
        WITH DESTINATION_TOPIC "devops/jira-cloud/issue/transition/response"
        WITH METHOD "POST"
        WITH ENDPOINT "/rest/api/3/issue/{value.json.issueIdOrKey}/transitions"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Content-Type" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"
        WITH BODY "{payload}"
    ADD EVENT Searchissuesjql
        WITH SOURCE_TOPIC "devops/jira-cloud/issue/search"
        WITH DESTINATION_TOPIC "devops/jira-cloud/issue/search/response"
        WITH METHOD "GET"
        WITH ENDPOINT "/rest/api/3/search/jql?jql={value.json.jql}&maxResults={value.json.maxResults}&fields={value.json.fields}"
        WITH HEADERS
            ADD "Accept" "application/json"
            ADD "Authorization" "Bearer {value.json.access_token}"

Events

Event	Method	Endpoint	Request topic	Response topic
Getmyself	GET	`/rest/api/3/myself`	`devops/jira-cloud/myself/get`	`devops/jira-cloud/myself/get/response`
Listprojects	GET	`/rest/api/3/project`	`devops/jira-cloud/project/list`	`devops/jira-cloud/project/list/response`
Createissue	POST	`/rest/api/3/issue`	`devops/jira-cloud/issue/create`	`devops/jira-cloud/issue/create/response`
Transitionissue	POST	`/rest/api/3/issue/{issueIdOrKey}/transitions`	`devops/jira-cloud/issue/transition`	`devops/jira-cloud/issue/transition/response`
Searchissuesjql	GET	`/rest/api/3/search/jql?jql=&maxResults=&fields=`	`devops/jira-cloud/issue/search`	`devops/jira-cloud/issue/search/response`

Auth

OAuth 2.0 (3LO) Bearer — default in the template:

Create an OAuth 2.0 (3LO) app in the Atlassian Developer Console with Jira scopes (classic read:jira-work / write:jira-work or equivalent granular scopes).
Obtain an access_token.
Set connector BASE_ADDRESS to https://{site}.atlassian.net.
Pass access_token on the MQTT request payload so headers resolve:
- Authorization: Bearer {value.json.access_token}
Store the token in Hub secrets / GET SECRET. Never commit real credentials.

Basic (email + API token):

Create an Atlassian API token for the integration account.
Prefer WITH USERNAME "you@example.com" and WITH PASSWORD GET SECRET "ATLASSIAN_API_TOKEN" on REST_API_CONFIG (remove Bearer header lines if using config Basic).

Example payloads

Create issue from alarm:

{
  "access_token": "YOUR_ACCESS_TOKEN",
  "fields": {
    "project": { "key": "OPS" },
    "issuetype": { "name": "Bug" },
    "summary": "Line sensor fault — Zone A",
    "description": {
      "type": "doc",
      "version": 1,
      "content": [
        {
          "type": "paragraph",
          "content": [
            { "type": "text", "text": "Vibration above threshold at 2026-10-04T00:00:00Z" }
          ]
        }
      ]
    }
  }
}

Transition issue:

{
  "access_token": "YOUR_ACCESS_TOKEN",
  "issueIdOrKey": "OPS-42",
  "transition": { "id": "31" }
}

Search issues (enhanced JQL):

{
  "access_token": "YOUR_ACCESS_TOKEN",
  "jql": "project = OPS AND statusCategory != Done ORDER BY updated DESC",
  "maxResults": "50",
  "fields": "summary,status,assignee,updated"
}

Deploy notes

Deploy JiraCloudRestApi.lot only (-addRoute). Do not deploy hub-metadata.lot as a connector — it exists for Hub / -listTemplates (ADD METADATA + WITH IMAGE base64).
Hub category: REST API Connectors.
Doc link: https://docs.coreflux.org/latest/lot-language/routes/rest-api-apps/jira-cloud

Quick Start

Coreflux MQTT Broker

LoT Language

Coreflux HUB

VS Code - LoT Notebooks

Coreflux Portal

Using AI with Coreflux

Product Updates

Overview

Basic Syntax

Events

Auth

Example payloads

Deploy notes

​Overview

​Basic Syntax

​Events

​Auth

​Example payloads

​Deploy notes

​Related

Overview

Basic Syntax

Events

Auth

Example payloads

Deploy notes

Related