Jira
What this is
Jira is a Hookshot™ integration that connects your Atlassian Jira instance to Hookshot. It enables three capabilities:
Trigger Access: Proteges can start runs in response to Jira events such as issue creation or status updates.
Tool Access: Proteges can use the full Jira API through Hookshot to create issues, update issues, add comments, and manage transitions.
Work Hub Provider Sync: You can link a Jira project, Jira Service Management (JSM) queue, or request type to a Work Hub project, importing issues as work items with full field mapping.
Jira does not support chat.
When to use it
When Jira events should start a Protege
When a Protege should create or update Jira issues as part of an automated workflow
When you want to mirror a Jira project into Work Hub so Hookshot becomes the control plane for triage, decisions, and follow-up work
What you need first
Access to the Jira instance you want to connect
Permission to complete the connection flow
A clear project, queue, or request type boundary for the automation
Steps
1. Connect Jira
Open Integrations.
Find Jira in the integration catalog.
Choose Connect and complete the connection flow.
Authenticate with your Jira instance and grant the requested permissions.
Confirm the integration shows as connected.
If your Jira instance uses custom authentication, contact Protege AI support for setup assistance.
2. Review Trigger Access
Use Trigger Access when Jira events should start the Protege.
Examples:
A new issue created in a selected project
An issue updated or transitioned
Configure the trigger to the narrowest project or queue boundary. Available inputs include project ID and project key.
If a Jira project is already managed by a Work Hub project, the Builder presents the Work Hub project as the scope instead of raw Jira triggers.
3. Review Tool Access
Use Tool Access when the Protege should take actions in Jira.
Examples:
Create a new issue
Update an existing issue
Add a comment
Manage status transitions
If a Jira project is managed by a Work Hub project, Work Hub policy mediates writes. The Protege cannot directly write to Jira for managed sources.
4. Set up Work Hub provider sync
You can link a Jira source to a Work Hub project so that Hookshot imports and tracks Jira issues.
In Work Hub, choose Create a project.
Select the Jira option.
Select a Jira connection (or connect one first if none exists).
Browse and select a Jira source: a project, JSM queue, or request type.
JSM stands for Jira Service Management. A JSM queue is a service desk queue that groups customer requests by category.
Configure the project details.
Confirm — Hookshot imports all issues, comments, attachments, approvals, and issue links from the selected source.
Jira provider sync uses periodic polling and reconciliation to import data into Work Hub. It does not push changes back to Jira — changes you make in Work Hub stay in Work Hub. Because Jira does not support managed event listeners, data updates appear after the next reconcile cycle rather than in real time.
What gets imported
Jira project, queue, or request type
Project with imported workstream
Jira issue
Work item with status, priority, assignee, custom fields
Jira comments
Comments
Jira approvals
Decisions
Jira attachments and remote links
Artifacts
Jira parent/epic links
Relationships
5. Review permissions
Review the Jira consent screen and allow only what your workflow needs. Hookshot™ needs permission to:
Observe the Jira items that should start the workflow
Access enough issue context to support the intended action
Read and write issues if the Protege will create or update them
Keep the scope limited to the relevant project whenever possible.
How to verify
Confirm Jira is connected in Integrations
Confirm the intended trigger source is live
Create a safe test issue in the selected project
Check Event Feed for the incoming activity
Check Audit for the resulting run
If using Work Hub, confirm the imported work items match the Jira source
Common failures
"No Jira account" appears in Work Hub — connect Jira in Integrations first, then return to Work Hub
"Reconnect Jira account" appears — the connection has expired or been revoked. Reconnect in Integrations.
Events never arrive in Event Feed — confirm the trigger source is enabled and the project boundary is correct
Work Hub project shows no imported items — confirm the Jira connection was fully finalized after the initial connection
Status changes do not push back to Jira — this is expected. Jira outbound projection is not supported. Changes stay in Work Hub.
Next step
Last updated
Was this helpful?