Jira Cloud integration

What it does

The Jira Cloud integration lets your agency manage every client's Jira site from a single workflow. Connect a client's site once and TaskJuice can create, read, update, and delete issues, comment on tickets, run JQL searches with offset-based pagination, list projects, and watch for new or changed issues on an interval.

Connect a Jira Cloud account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Jira Cloud and click Connect.
3. Sign in with the Atlassian user whose Jira site you want to manage on behalf of your client.
4. Approve the requested scopes (read:jira-work and write:jira-work for the issue surface, manage:jira-webhook for future webhook support, offline_access so TaskJuice can refresh access tokens without re-prompting).
5. Pick the Atlassian cloud ID for the client's site when prompted. Atlassian returns the list of authorized sites after sign-in; the cloud ID you select scopes every subsequent API call to that site.
6. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, the connected user can open id.atlassian.com, go to Account settings, choose Connected apps, and revoke the TaskJuice entry.

Triggers

• jira-cloud/issue-changed polls Jira on a configurable interval and emits one cycle per poll containing every issue whose updated timestamp advanced past the prior watermark. Configure a base JQL filter (e.g. project = ENG), the field projection, and the polling cadence. Drop a Loop node downstream to fan out one branch per issue.
• jira-cloud/project-created polls the Jira project search endpoint on an hourly default and emits any project whose id has not been observed in a prior cycle. Drop a Loop node downstream to fan out per project.

Jira Cloud also exposes an app-level webhook REST API, but those webhooks are unsigned (URL-secret only) and so do not satisfy the declarative inbound-auth requirement. TaskJuice ships polling as the declarative path. Reach out if your client's site needs signed real-time delivery and we will provision a bespoke workflow.

Actions

• jira-cloud/get-issue reads a single issue by key or numeric ID, with an optional projection of the fields to return.
• jira-cloud/create-issue creates a new issue in a project, using the Atlassian Document Format for the description.
• jira-cloud/update-issue patches one or more fields on an existing issue and applies field-level update operations (add or remove labels, components).
• jira-cloud/delete-issue removes an issue and optionally cascades to its sub-tasks.
• jira-cloud/add-comment adds a comment to an issue using the Atlassian Document Format, with an optional visibility restriction.
• jira-cloud/search-issues runs a JQL query and returns matching issues with offset-based pagination (startAt + maxResults).
• jira-cloud/list-projects lists projects visible to the authorized user with offset-based pagination.

Known limitations

• Atlassian enforces per-app and per-tenant rate limits on the Jira Cloud REST API. When the upstream returns a 429, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.
• The polling trigger watermarks on the issue updated timestamp, which has one-second resolution. Issues edited within the same second as the prior watermark may be emitted twice; the connected workflow should dedupe on id if exactly-once semantics matter.
• Jira webhooks ship without HMAC signing and so are not used. Real-time delivery for Jira Cloud requires a bespoke connector outside the declarative envelope.
• Each Jira site has a separate Atlassian cloud ID. Connecting more than one site for the same client requires one connection per site so workflows can target the correct cloud ID.