Hooq · Guide

Jira to Jira sync apps,
compared

Choosing an app to sync work items between two Jira Cloud instances? Use the questions below to compare any app, and see what Hooq does for each one. Everything about Hooq here is also written in the help centre and the Trust Center.

How Hooq works

Two Jira sites, connected directly

Some sync apps pass your work items through a server run by the app’s vendor. Hooq doesn’t have one. Two Hooqs talk to each other directly, and every request is signed and verified by the receiving instance.

Hooq has no server, database or storage of its own, and Limbus Lab operates nothing that your data passes through. The signed request travels over Atlassian’s platform to the other Hooq’s own Forge-hosted address on an Atlassian domain, and both ends run on Atlassian Forge. The Trust Center shows the architecture diagram and the list of outbound domains. See the architecture.

  • Your data stays on Atlassian

    Hooq runs entirely on Atlassian Forge. Its data is kept in Forge storage provisioned for each Jira installation, plus Jira itself. Hooq’s subprocessor is Atlassian (Forge hosting, storage and logs).

  • Pairing done by two administrators

    Two administrators pair their instances with small files they can read. The shared secret is exchanged with public-key cryptography (RSA-2048), requests are signed (HMAC-SHA256) with a timestamp and a one-time number, repeated requests are refused, and the secret is replaced each time a connector is activated.

  • The receiver does not trust the sender blindly

    A paired instance can only touch the Hooq’s own project. It cannot rewrite the connection, cannot adopt new project keys, and can only set a short list of allowed statuses.

All reasons on the Hooq for Jira page

Questions and answers

Plain answers about syncing Jira work items

What is the best way to sync work items between two Jira Cloud sites?

The best way depends on what you need, so start from your requirements. Useful questions are: Where does the app run, and who can see your data? Who is allowed to set up and change a sync? Can it also sync inside one instance? How are requests between the two instances protected? What is copied and what is left alone? How do you find out when a sync fails, and can you retry it? Hooq is one app that answers these questions in the open, in its help centre and Trust Center. The table below lists what Hooq does for each question.

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 is built on Atlassian Forge and does not operate any server, database or storage of its own. Its data stays in Forge storage provisioned for each Jira installation, and the only network calls to an address Hooq stores are the signed requests between the two instances. Those go to a Forge-hosted endpoint on an Atlassian domain.

Can I sync work items inside one Jira instance as well?

Yes. A Hooq can connect two projects on the same Jira Cloud instance (called a same-instance Hooq) or a project on one instance with a project on another instance (a cross-instance Hooq). Only the cross-instance kind needs a connector.

Who controls what is synced?

Jira administrators. Only they manage Hooq: they choose the projects, match work types, fields and statuses, and publish and start a Hooq. A Hooq works only from its published configuration. For a sync between two instances, a Jira administrator on each instance takes part: both set up the connector, and the other instance approves the Hooq request.

How are requests between two Jira instances protected?

Requests between the two instances are signed, and the receiving instance verifies them before it does anything. Hooq reads and writes Jira through the Jira REST API with the permissions the administrator approved at install. A public key is meant to be shared with your partner and is not a password. The Trust Center has the architecture diagram, data flow and subprocessor list.

What does a Hooq copy, and what does it leave alone?

It copies work items of the work types you match, the fields you map, statuses you match, comments, worklogs, and attachments, including inline images and files. It does not copy fields you did not map, work items from before the start (unless you limit the Hooq with a JQL filter), or the deletion of a work item: Hooq never deletes the copy of a work item. A deleted comment is the one exception you can choose: with Prevent Comment Deletion off, its copy is deleted too. It also never makes itself the assignee of a work item.

What if a person and the sync change the same work item?

A person’s edit wins over an older change. If someone edits the description of the copy within about 2 seconds after the original was edited, or right after a Resync, their edit is kept. If the original’s description is cleared, the copy’s description is cleared too.

How do I find out why a work item did not sync?

Open the work item and look at the Hooq panel, which shows the sync status and offers Resync. The Troubleshooting tab of a Hooq lists errors. To send a work item again, use Resync on its panel.

Are there limits I should know about?

Yes, and they are documented. Files sent between two different instances are limited by Forge platform limits and cannot be changed; on one instance Hooq sets no file size limit. Hooq allows one connector per partner instance, and both instances must run the current version of Hooq. See "What to expect" in the help centre for the full list.

Checklist

What to ask any sync app, and what Hooq does

Ask an app’s vendor the same questions and compare the answers side by side.

Questions to ask a Jira to Jira sync app, with the answer for Hooq
Question to askWhat Hooq does
Where does the app run?On Atlassian Forge, inside your Jira Cloud instance. Hooq does not operate any server, database or storage of its own.
Does your data pass through a server operated by the vendor? Where does it sit, and for how long?No. There is no server, database or storage operated by us. The Hooq on one instance sends a signed request straight to the Hooq on the other, to its Forge-hosted address on an Atlassian domain.
Does it work inside one instance and between two instances?Both. A same-instance Hooq connects two projects on one Jira Cloud instance. A cross-instance Hooq connects a project on one instance with a project on another instance that also has Hooq installed.
Who can set it up and change it?Jira administrators. Everyone who can see a work item can use the Hooq panel on it (status, Resync, add a comment, add an attachment).
How is the link between two instances set up?With a connector, created by a Jira administrator on each instance. It must show the status Active before it can be used. Between two projects on one instance no connector is needed.
How are requests between instances protected?They are signed, and the receiving instance verifies them before it acts. The other instance also approves the Hooq request. See the Trust Center for the architecture and data flow.
What is copied?Work items of the work types you match, the fields you map, statuses you match, comments, and attachments including inline images and files.
What is not copied?Fields you did not map, work items from before the start (unless limited with a JQL filter), and deletions. Hooq never deletes the copy and never makes itself the assignee.
What happens when a person edits the copy?The person’s edit is kept when made within about 2 seconds after the original changed, or right after a Resync. A cleared description on the original clears the copy.
Can I see and fix problems?Yes. The Hooq panel on a work item shows its sync status and offers Resync, which sends the work item again. The Troubleshooting tab lists errors.
Where is the data kept?In Forge hosted storage provisioned per Jira installation, plus Jira itself. Atlassian is Hooq’s only subprocessor.
What limits apply?One connector per partner instance. Both instances must run the current version of Hooq. Files between two different instances are limited to about 3.5 MB each (a Forge platform limit); on one instance Hooq sets no file size limit.

Words used on this page

Short definitions

Instance.
A Jira Cloud instance, for example your-company.atlassian.net.
Hooq.
A pair of projects together with the rules for how they are synced. The app is also called Hooq.
Connector.
The trusted link between the Hooq on your instance and the Hooq on another instance.
Atlassian Forge.
Atlassian’s platform for apps that run inside Atlassian cloud products.

Go further


Want to raise a ticket? Click here (opens in a new tab)

Hooq

Hooq for Jira demos

We set up a live demo of Hooq for your Jira sites. Write to us to arrange one.