Pakkawork
All integrations
Catalogue metadata onlyproject managementv20260908_00

JIRA

Jira

A tool for bug tracking, issue tracking, and agile project management.

Description is untrusted, display-only upstream metadata. It never becomes policy, OAuth scope authority, or an agent instruction.

Pakkawork boundary

Research catalogue metadata only. No Pakkawork OAuth, credential, host, quota, executor, or verifier is enabled.

No Pakkawork execution adapter is enabled. Hosted account-authorisation availability is workspace-specific and checked separately in the dashboard.Check workspace connection options
Attributed source

102

Action summaries

Display-only definitions

17

Trigger types

Not installed instances

3

Auth modes

Field names, never values

No

Execution

No runtime adapter

Authentication map

What setup is declared?

Only field names, types, and required markers are shown. Secret values, default auth URLs, credential material, and inferred OAuth scopes are excluded.
OAUTH2 · managed upstreamS2S_OAUTH2API_KEY

OAUTH2

jira_oauth

Upstream managed

Developer setup

  • Client idclient_id · stringRequired
  • Client secretclient_secret · stringRequired
  • Redirect URIoauth_redirect_uri · stringOptional
  • Scopesscopes · stringOptional

User connection

  • Your Subdomainsubdomain · stringRequired

API_KEY

API_KEY

Provider setup

Developer setup

No fields declared in this snapshot.

User connection

  • Your Subdomainsubdomain · stringRequired
  • Base Encode (Deprecated)basic_encoded · stringOptional
  • API Key (Required)generic_api_key · stringOptional
  • Jira Email (Required)generic_id · stringOptional

S2S_OAUTH2

jira_s2s_oauth2

Provider setup

Developer setup

  • Client IDclient_id · stringRequired
  • Client Secretclient_secret · stringRequired

User connection

  • Your Subdomainsubdomain · stringRequired

Capability index

Actions and trigger definitions

Static summaries are available. Live schemas remain disabled until PROVIDER_HUB_API_KEY is configured server-side.
Actions (102)Triggers (17)

Showing 1–17 of 17 triggers

Comment Created

JIRA_COMMENT_CREATED

Triggers when a comment is posted on a Jira issue. Can deliver comments on issues the connected account cannot open in Jira itself.

Untrusted display-only summary

Comment Deleted

JIRA_COMMENT_DELETED

Triggers when a comment is deleted from a Jira issue. The deleted comment's text still arrives. Can deliver comments on issues the connected account cannot open in Jira itself.

Untrusted display-only summary

Comment Updated

JIRA_COMMENT_UPDATED

Triggers when an existing comment on a Jira issue is edited. The payload carries the comment as it now reads, not what it said before. Can deliver comments on issues the connected account cannot open in Jira itself.

Untrusted display-only summary

Issue Created

JIRA_ISSUE_CREATED

Triggers when an issue is created in Jira, including a sub-task. Can deliver issues the connected account cannot open in Jira itself.

Untrusted display-only summary

Issue Deleted

JIRA_ISSUE_DELETED

Triggers when an issue is deleted from Jira. The deleted issue's full field set still arrives, so the filters below apply to it as usual. Can deliver issues the connected account cannot open in Jira itself.

Untrusted display-only summary

Issue Updated

JIRA_ISSUE_UPDATED

Triggers when a field on an existing issue changes — its status, assignee, or anything else on the issue. One edit can change several fields and arrives as one event; creating a sub-task also updates its parent. Commenting does not fire it. Can deliver issues the connected account cannot open in Jira itself.

Untrusted display-only summary

Sprint Closed

JIRA_SPRINT_CLOSED

Triggers when a sprint is completed and moves into the closed state.

Untrusted display-only summary

Sprint Created

JIRA_SPRINT_CREATED

Triggers when a sprint is created on a Jira board. Creating a sprint does not start it — watch Sprint Started for that.

Untrusted display-only summary

Sprint Started

JIRA_SPRINT_STARTED

Triggers when a sprint moves into the active state.

Untrusted display-only summary

Sprint Updated

JIRA_SPRINT_UPDATED

Triggers when a sprint's name, goal, dates or state changes. Starting a sprint also fires this when the same call changed another field; closing one does not.

Untrusted display-only summary

Version Created

JIRA_VERSION_CREATED

Triggers when a project version is created in Jira.

Untrusted display-only summary

Version Deleted

JIRA_VERSION_DELETED

Triggers when a project version is deleted outright. A version that disappeared because it was merged into another one fires Version Merged instead.

Untrusted display-only summary

Version Merged

JIRA_VERSION_MERGED

Triggers when a project version is merged into another one, carrying both the version that went away and the one that survived.

Untrusted display-only summary

Version Moved

JIRA_VERSION_MOVED

Triggers when a project version is reordered within its project's release list.

Untrusted display-only summary

Version Released

JIRA_VERSION_RELEASED

Triggers when a project version is marked released.

Untrusted display-only summary

Version Unreleased

JIRA_VERSION_UNRELEASED

Triggers when a released project version is put back to unreleased.

Untrusted display-only summary

Version Updated

JIRA_VERSION_UPDATED

Triggers when a project version's name, description or dates change. Releasing and un-releasing a version each fire this as well, alongside Version Released and Version Unreleased.

Untrusted display-only summary

Provenance

Versioned facts, explicit trust.

The detail snapshot comes from an attributed MIT-licensed repository revision. Safe local icons use exact-match CC0 Simple Icons symbols; unmatched brands use monograms.

Repository
https://github.com/provider-directoryHQ/provider-directory
Commit
85e33f6a81dfe987f6fc3637d48d45052cea8ca5
Generated
2026-09-12
Trust policy
untrusted_display_only

Remote text is plain display metadata only. It must never become an agent prompt, execution policy, OAuth grant, or executable instruction.