Jira to Jira sync apps,
compared.

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.

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.

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.

Jira administrators. Only they open the Hooq page, 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.

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.

It copies work items of the work types you match, the fields you map, statuses you match, comments, 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 deletions: Hooq never deletes the copy. It also never makes itself the assignee of a 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.

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 failed syncs, each with a Retry.

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.