feat: add Jira heartbeat management components

[felixgateru]

Resolves #4893

What changed

Adds four Jira Service Management (JSM) Operations workflow components:

• Create Heartbeat — register a new heartbeat monitor (interval, alerts, etc.)
• Ping Heartbeat — report liveness for an existing heartbeat
• Update Heartbeat — change heartbeat settings (optional fields via toggles)
• Delete Heartbeat — remove a heartbeat from a team

Why

Enable Superplane workflow to manage Jira Heartbeats that detects when scheduled jobs, cron tasks, or automated systems stop reporting in. If a heartbeat is not pinged within its expected interval, Jira Service Management raises an alert.

How

Backend:

Implemented new client methods in pkg/integrations/jira/client.go for heartbeat endpoints.
Registered actions in pkg/integrations/jira/jira.go and updated token permission guidance.
Added tests

Frontend:

Added Jira workflow v2 mappers
Registered mappers and event states in web_src/src/pages/workflowv2/mappers/jira/index.ts
Added mapper specs

[superplanehq-integration]

👋 Commands for maintainers:

• /sp start - Start an ephemeral machine (takes ~30s)
• /sp stop - Stop a running machine (auto-executed on pr close)

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 1f4133d. Configure here.}

[cursor]

Update setup allows empty toggles

Medium Severity

Setup treats any enabled toggle as an update via hasAnyHeartbeatUpdate, but Execute builds the PATCH with updateHeartbeatRequestFromSpec and rejects when updateHeartbeatRequestEmpty (e.g. empty description, empty alert tags, or interval under 1). Nodes can save yet fail at run with "at least one update field must be enabled".

 

^{Reviewed by Cursor Bugbot for commit 1f4133d. Configure here.}

[cursor]

Create sends disabled by default

Medium Severity

Execute always sets CreateHeartbeatRequest.Enabled from spec.Enabled, a plain bool that is false when the key is absent after decode. That can POST "enabled": false despite the field default of true, creating disabled heartbeats unless the UI always persists enabled.

 

^{Reviewed by Cursor Bugbot for commit 1f4133d. Configure here.}