Jira Data Center

Overview

Connect Jira Data Center with Flows360

Issue tracking and project management for Jira Data Center and Server

Use the Jira Data Center connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 15 actions and 3 triggers.

Available actions

• Create Issue
• Update Issue
• Get Issue
• Find User
• Search Issues
• Assign Issue
• Add Attachment to Issue
• Get Issue Attachment
• Plus 7 additional declared actions.

Available triggers

• New Issue
• Updated Issue
• Updated Issue Status

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

• Connector: Jira Data Center
• Package: @activepieces/piece-jira-data-center@0.1.0
• Exact artifact digest: sha256:c5b7b82059bd0e817423ee429f2ef7eda6d5b065e495da84d9cfef342112ef4c
• Runtime: Activepieces-compatible deterministic worker
• Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

• Create Issue (create_issue), Creates a new issue in a project. Classification: read.
• Update Issue (update_issue), Updates an existing issue. Classification: read.
• Get Issue (get_issue), Get issue data. Classification: read.
• Find User (find-user), Finds an existing user. Classification: read.
• Search Issues (search_issues), Search for issues with JQL Classification: read.
• Assign Issue (assign_issue), Assigns an issue to a user. Classification: read.
• Add Attachment to Issue (add_issue_attachment), Adds an attachment to an issue. Classification: read.
• Get Issue Attachment (get-issue-attachment), Retrieves an attachment from an issue. Classification: read.
• Add Watcher to Issue (add-watcher-to-issue), Adds a new watcher to an issue. Classification: read.
• Add Issue Comment (add_issue_comment), Adds a comment to an issue. Classification: read.
• Update Issue Comment (update_issue_comment), Updates a comment to a specific issue. Classification: read.
• Link Issues (link-issues), Creates a link between two issues. Classification: read.
• List Issue Comments (list_issue_comments), Returns all comments for an issue. Classification: read.
• Delete Issue Comment (delete_issue_comment), Deletes a comment on a specific issue. Classification: read.
• Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

• New Issue, polling.
• Updated Issue, polling.
• Updated Issue Status, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authentication

Authentication method: custom

Authentication profiles

Supported objects

Triggers

Setup

Setup

1. Add the Jira Data Center connector to the workflow in the target Flows360 Studio instance.
2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
3. Provide the connection fields declared by the pinned package:

• Instance URL (instanceUrl), required.
• Personal Access Token (personalAccessToken), required; stored as a sensitive connection value.

1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

• This content describes @activepieces/piece-jira-data-center@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 15 actions and 3 triggers declared by this pinned package are represented here.
• Tenant credentials and connection values are not stored in the public connector record.
• Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
• Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Related documentation