Hooq - Work Items in Jira
Work Item Synchronization between connected Jira Cloud sites
A Forge-based Jira Cloud app that synchronizes work items between two Jira Cloud instances or within the same instance. Connections are configured by administrators and data stays within Jira Cloud with no external servers or third-party processing.
Complete Product Overview
Watch the full walkthrough before exploring key features.
Key Features
Forge-Based Execution
Operates within Jira Cloud using Forge and the permissions granted during installation.
Direct App-to-App Links
Connect two Jira Cloud sites with secure app-to-app communication and no central server.
Field Mapping
Map standard and custom fields, statuses, priorities, and users for consistent work items.
Workflow Alignment
Align statuses and transitions so workflows stay consistent across connected projects.
Granular Sync Control
Use project filters or JQL to define what should sync and when.
Loop Prevention
Correlation tracking prevents duplicate updates and infinite sync loops.
Hooq Features
Designed for secure, direct, and controlled synchronization between Jira Cloud sites.
Hooq runs natively inside the Atlassian Forge runtime — the secure, serverless execution environment embedded within Jira Cloud. No external infrastructure to manage, provision, or trust. The app operates entirely within the Atlassian ecosystem, using only the permissions granted during installation.
Hooq has no central servers — not hidden ones, not third-party ones, none. Every sync happens directly between two Jira Cloud installations. Your data is never routed through an intermediary, buffered on external infrastructure, or moved outside the Atlassian environment without your explicit configuration.
Each installation generates its own cryptographic identity. A shared secret is established during activation and stored exclusively within Forge's secure storage — inaccessible to your site admins, to Hooq admins, and to us. Every sync request is signed and cryptographically verified before any data moves.
Because Hooq operates entirely within Jira Cloud, it inherits your site's data residency configuration automatically. We do not independently process, copy, or route your data to external locations. What your residency policy keeps in-region, Hooq keeps in-region.
Hooq syncs only what you explicitly configure — nothing extra is collected, monitored, or stored in the background. No behavioral tracking, no analytics pipelines, no telemetry collection, no advertising integrations. You are not the product.
By executing directly on Forge and communicating through Jira Cloud APIs, Hooq eliminates external routing latency. Every sync request is signed, verified, and dispatched without unnecessary hops — delivering consistent, predictable updates between instances.
Hooq inherits Forge's native permission model, runtime isolation, and authentication framework — security is not bolted on, it is foundational. Every connector operates independently. Every request is cryptographically verified. No shared processing hub, no single point of failure.
Hooq ships through the Atlassian Marketplace and updates automatically through Jira's standard app lifecycle. No servers to patch, no deployments to schedule, no infrastructure to maintain. Install once, and Hooq keeps itself current.
Synchronization Capabilities
Flexible controls to keep work items aligned without sacrificing local workflows.
Synchronize work items between two Jira Cloud sites — or across projects within the same site — using secure, direct app-to-app connections. Each connector is independently configured and operates in isolation.
Map standard and custom fields — status, priority, assignee, issue type, and any custom field — across connected instances. Keep data consistent without forcing identical field structures on either side.
Map statuses and transitions between sites so work items stay in sync through their lifecycle without requiring identical workflows. Each site can follow its own process while remaining aligned with the other.
Synchronize comments with optional visibility controls, attachments, worklogs, sprints, and boards. You decide what is shared across sites and what stays local — nothing is synced without explicit configuration.
Use JQL filters or project-level rules to define exactly what syncs, what stays local, and when synchronization triggers. Full control over scope means no unwanted data crossing boundaries.
Built-in correlation tracking detects and blocks duplicate updates, circular sync chains, and infinite loops before they propagate. Every update is identified and verified — changes only move when they should.
Multi-Directional Relationships
Control how each work item connects across Jira Cloud sites.
A single work item can be connected to multiple issues across different sites, or you can configure strict one-to-one synchronization.
Each connected issue appears inside the Hooq Sync Panel on the work item, placed alongside linked items for quick access.
From there, you can:
- View linked issues
- Communicate individually without broadcasting to all
- Check remote issue status (if shared)
- Restrict what is synchronized
Synchronization is controlled — not automatic broadcasting.
Direct, Verified Communication
A trust model built on explicit approval and cryptographic verification.
Hooq installations talk directly to each other.
There is no central server routing traffic between instances.
Every request is signed and verified. Every connector operates independently.
Every connection is explicitly approved.
The Result
- Explicit trust
- Controlled data movement
- Cryptographic verification
- Infrastructure simplicity
- Enterprise clarity
Hooq does not just connect Jira sites. It connects them deliberately.
Built With
Frontend
- Forge Custom UI
- React
- TypeScript
- @forge/bridge
Backend
- Forge functions
- Forge storage
- Jira REST API
Infrastructure
- Atlassian Forge
- Jira Cloud