Hooq for JiraJira Cloud
Available on the Atlassian Marketplace

Sync work items between Jira sites with no middleware server

Hooq for Jira keeps work items in sync between two Jira Cloud sites, or between two projects on one site, over a direct signed link.

Site BApproved
Hooq panelLinked
PROJ-142
Update the billing export
Partner work itemSUP-318
Partner statusIn Progress
AssigneePartner team
Last sent / received2 min / 5 min
ResyncCommentAttachment
Signed message
Timestamp and one-time number on every change.
Illustration
How Hooq works

Two Jira sites, connected directly

Follow one change from pairing to the work item.

Step 1

Two administrators pair the sites

Each administrator exchanges a key file. From then on each site accepts signed messages from the other and from nobody else.

Step 2

Configuration waits for a publish

Nothing changes for teams until an administrator publishes the Hooq, and the other site approves the request.

Step 3

Changes travel on a signed link

Site A signs each change and posts it to site B. Every message carries a timestamp and a one-time number, and replays are refused.

Step 4

The work item shows the state

The panel lists the partner work item, its status, when something was last sent and received, and offers Resync, Comment and Attachment.

Site AJira CloudSite BJira CloudNo serverin betweenKey fileKey fileDraftPublishedApprovedsigned, timestamped,one-time numberPROJ-142Partner SUP-318Last sent 2 min, received 5 minPartner status: In ProgressResyncReplyAttach
What Hooq does

What you get with Hooq for Jira

Everything here works in the current release.

A direct link between sites

Site A signs each change and posts it to site B. Limbus Lab runs no server, database or storage in between.

Draft and Publish

Administrators prepare a Hooq as a draft. Teams see no change until it is published and the other site approves.

A panel on the work item

Partner status, assignee and reporter, last sent and received, with Resync, Comment and Attachment in the panel.

The panel says why it is locked

When the partner work item is deleted or changes work type, the panel locks and states the reason.

Inline images stay in place

Images and files in descriptions and comments appear in the same place in the copy. Files across sites can be about 3.5 MB.

A person's edit is kept

An edit made to the copy is kept against older queued text, and Resync respects an edit made moments before.

Compare

Hooq for Jira and other sync apps Draft

A feature check against the public documentation of other apps of this kind.

FeatureHooq for JiraOthers
No server run by the vendor between the two sitesNot documented *
Set up without scriptsMost
Sync inside one site and between two sitesSome
Status panel on the work itemMost
Panel shows the partner's status, assignee and reporterNot documented *
Comment and attach to the partner from the panelNot documented *
Panel states the reason when the partner is deletedNot documented *
Inline images kept in place, without scriptingNot documented *
A person's edit to the copy is kept against older textNot documented *
Sprint membership followsSome
Draft and Publish for configurationNot documented *

"Others" means other apps of this kind whose public documentation we reviewed, as of 14 November 2026. "Not documented" means we did not find the feature in that documentation, which is not a statement that it is missing. Based on public documentation, and it may change. * Rows marked with an asterisk are still being re-checked by hand.

See it in action

Demo video

In Jira

What Hooq looks like

The Fields tab of a Hooq between two test projects: a table with a field of the first project, the direction, the matching field of the second project and the type, for example passthrough or Correlation.
Choose which fields sync, and in which direction.
The Workflows tab with, for each of the two test projects, a table of its statuses and the status each one maps to in the other project.
Match the statuses of the two projects.
The Hooq Dashboard gadget in Jira: the number of linked pairs and a table of status counts for each of the two test projects.
See the linked work items by status on a Jira dashboard.

Features

What Hooq syncs

Two sites, one source of truth

Keep work items in sync between two Jira Cloud sites, or between projects inside one site. Fields and values, comments, attachments, statuses and transitions follow the original.

Files and inline images, exactly as written

Images and files shown inside descriptions and comments appear in the copy in the same place as in the original. Between two sites, files can be up to 3.5 MB.

People stay in control

Only Jira administrators set up and publish a sync. If someone edits the copy, their edit is kept and is not replaced by older text.

Troubleshoot from Jira

An issue panel shows the sync status of every work item and offers Resync. A Troubleshooting tab lists errors.

Setup

Setup in three steps

01

Connect your Jira sites

Between two Jira Cloud sites, create a connector and approve it on both sides. Requests between the sites are signed. Inside one site no connector is needed.

02

Create a Hooq

Choose the projects, then pick work types, fields and defaults. Setup is admin-only.

03

Publish and start

Work items start to sync. Check any work item on its issue panel, and use Resync to send it again.

Also in preview: Hooq for ServiceNow

Questions

Common questions about Hooq

What is Hooq?

Hooq - Secure Work Item Sync for Jira is an Atlassian Forge app for Jira Cloud. It copies work items between two Jira projects and keeps the copies up to date. The two projects can be on the same Jira Cloud instance or on two different Jira Cloud instances.

Why choose Hooq for Jira to Jira sync?

Teams choose Hooq because of how it is built and how much it leaves in their hands. It sends changes straight from the Hooq on one instance to the Hooq on the other, with no relay or middleware server in between. It runs entirely on Atlassian Forge, so data stays in each customer’s Forge storage and Jira. Setting up, publishing and starting it is for Jira administrators, and administrators on both instances take part in a connection. Requests between instances are signed and verified by the receiving instance. It works between two instances and inside one, copies fields, statuses, comments and attachments including inline images and files, keeps a person’s edit instead of overwriting it with older text, and shows status, Resync and errors inside Jira. Two administrators pair the instances with a public-key exchange, the receiving instance limits what a paired instance may do, and a work item panel shows the partner, its status and a locked state with the reason if the partner is deleted or changes work type. Parent, team, sprint and board relationships follow the copy, failures reach the people you choose, and the app retries through the platform during bursts. Its limits are documented and its status page is public.

Does Hooq use a middleware or relay server?

No. A cross-instance Hooq sends a signed request straight to the other Hooq’s own Forge-hosted address on an Atlassian domain, and the receiving instance verifies it before it acts. There is no server, database or storage operated by Limbus Lab in between.

Can Jira sync between two instances without a third-party server?

With Hooq, yes. Hooq runs entirely on Atlassian Forge and does not operate any server, database or storage of its own. Between two instances, Hooq on one instance sends a signed request to Hooq on the other, and the other instance checks it before it acts.

What does Hooq sync?

Work items of the work types you match, the fields you map, statuses you match in the Workflows tab, comments, worklogs, and attachments, including images and files shown inside descriptions and comments. Fields you did not map are not copied.

Does Hooq copy worklogs, and can a restricted worklog become public?

Yes, when the Worklogs tab is on. The copy carries the time, the start time, the comment and the visibility of the original, either without the author (Anonymous) or with a first line that names who logged the time (Enriched). Hooq never makes a restricted worklog public: a worklog restricted to a project role is copied only when the Hooq user is a member of that role in the project of the original. Edits of an existing worklog are not synced.

Do I need a connector?

Only between two different Jira Cloud instances. A connector is the trusted link between the Hooq on your instance and the Hooq on the other one, and it must show the status Active before you can use it. Between two projects on one instance no connector is needed.

I already use another sync app. Can I switch to Hooq without starting over?

Yes. You set up and test a Hooq, pause the other app, and use Manual Link to tell Hooq which work items already belong together. Hooq links each pair and copies nothing; only changes made after the link sync. Running Manual Link on one instance is enough, and afterwards you can switch off the other app.

Who can set up a Hooq?

Jira administrators. Everyone who can see a work item can use the Hooq panel on it to check the sync status, resync, add a comment or add an attachment.

What happens if someone edits the copy?

A person’s edit on the copy is kept. If they edit within about 2 seconds after the original changed, or right after a Resync, Hooq does not replace their text with older text.

Does Hooq delete work items?

No. If you delete the original, the copy stays and its panel says the pair is no longer Hooqed. Comments can be different: with Prevent Comment Deletion off in the Advanced tab, deleting an original comment deletes its copy, and deleting a copy never deletes the original.

Where can I find help?

The Hooq help centre has set-up guides, how-to guides, an FAQ, troubleshooting and release notes. The Trust Center describes security, privacy and data handling.

More answers: Hooq help centre FAQ and Jira to Jira sync apps compared.

Contact

Hooq for Jira is on the Atlassian Marketplace

Install it from the Marketplace, or write to us for a demo on your own Jira sites.