Hooq for Jira.
Jira to Jira sync with nothing in the middle.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.