FAQ

Between two different Jira instances, a file can be up to about 3.5 MB. This is a Forge platform limit and it cannot be changed. On one instance, Hooq sets no size limit.

Hooq does not copy that file. The rest of the work item still syncs. An error such as Attachment not copied: report.pdf (4.2 MB) is larger than the cross-instance limit of 3.5 MB appears in the Troubleshooting tab. Attach the file to the other work item by hand, or make it smaller and upload it again.

Yes. Images and files shown inside a description or a comment appear in the copy in the same place as in the original.

Your edit on the copy is kept if you make it within about 2 seconds after the change to the original, and also right after a Resync. Hooq does not silently replace your text with older text.

The description of the copy is cleared too.

Most likely the status of the original is not matched in the Workflows tab. Add a match for that status, publish, and change the status again. See Troubleshooting.

The Sync Assignee setting is turned off for this Hooq, so the panel does not show the other work item's assignee. This setting only changes what the panel shows; it does not stop a mapped Assignee field from being copied. You can change it in the Advanced tab (Sync Assignee).

Open the work item and look at the Hooq - Work Sync Panel. The Hooqed With row links to the other work item.

Not a work item. Hooq never deletes work items. The copy stays and its panel says the pair is no longer Hooqed. A comment is different: if you turn Prevent Comment Deletion off in the Advanced tab, deleting the original comment deletes its copy.

Not by default. Starting a Hooq without a JQL filter in Limit Work Items (Work Types tab) does not copy existing work items, and Resync only updates work items that already have a copy. To link pairs you already have from another sync app, see How to link existing work items from another sync app.

While Prevent Comment Deletion in the Advanced tab is on (the default), copies of comments are kept. If it is off and the copy is still there, the comment was copied before this release, the Hooq was stopped when you deleted it, or the comment you deleted was itself a copy. Deleting a copy never deletes the original.

In the Comments tab, Comment as Hooq copies the plain comment without the line that says who wrote it. Comment as actual author keeps that line. In both cases the copy is posted by Hooq.

Anonymous copies the time, the start time, the visibility and the comment and says nothing about who logged the time. Enriched adds a first line such as Worklog by Developer – Oct 17, 2026, 6:52 PM to the comment of the copy. User-based no longer exists; a Hooq that had it behaves as Enriched.

The Worklogs tab may be on Disabled, or the worklog may be an edit (edits are not synced) or a copy made by Hooq. 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; otherwise it is not copied and never made public. See Worklogs.

Refresh Boards and the filter dropdown list only the boards and filters whose Jira filter the Hooq app can see. Share the filter with the project, then refresh.

Jira’s API cannot rename a board, so Hooq cannot sync a rename. Board Updated and Configuration Changed only create the partner board if it is missing.

Yes, when the parent is also synced in the same Hooq: the copy is moved under the copy of that parent, for an existing work item and for a new one. A removed Parent is not cleared on the copy, and a field mapping to Parent replaces this behaviour. See Fields and values.

Only if you use Limit by Filter in the Work Types tab, tick Sync comments or Sync worklogs and publish. Hooq then copies the existing comments and worklogs of the filter’s work items when it starts, without copying anything twice. See Work types.

Yes. Set up and test your Hooq, pause the other app, and use Manual Link to tell Hooq which work items already belong together. Hooq links each pair and nothing is copied. After that you can switch off the other app. Steps: How to link existing work items from another sync app.

No. Hooq only links the pairs. Comments, files and fields that both work items already have stay as they are. Only changes made after the link sync, and a Resync does not send the history again.

No. Run it on either instance. The other instance learns about the link from the first change Hooq sends for the pair. Running it on both is harmless.

The list shows text fields first. If the key is kept in a label or a select list, tick Show all fields. If the list is empty, open the Hooq tab, select Refresh Project Details and come back. Jira's own Parent field is only listed under Show all fields.

Jira administrators manage Hooq. Another user who opens Hooq from the Apps menu sees the note Hooq is managed by Jira administrators. and cannot change or run anything there. Every user who can see a work item can use the Hooq panel on it: Resync, add a comment and add an attachment.

Yes, in three ways: a connector is needed between different instances, the other instance must approve the Hooq request, and files between different instances are limited to about 3.5 MB. Everything else works the same.

A Hooq works from the published configuration. Select Publish Draft after you change a tab.

Only for a Hooq between two different Jira instances. A Hooq between two projects on one instance needs none. See Connectors.

Open Hooq from the Apps menu, select ... next to New Hooq, then Connectors.

No. Hooq allows one connector per partner instance and refuses a second one, whatever you name it. Use Activate or Reconnect on the existing connector, or delete it first.

No. A public key is meant to be shared with your partner. Hooq never asks you to share anything else.

Yes, if its content is right. Hooq reads the content of the file and not its name. It shows a warning if the name does not match the instance inside the file.

5 minutes. If it is older, generate a new one.

Hooq keeps it as a Draft. Open it from the Connectors page and continue. You can have up to 5 drafts; delete the ones you do not need.

Yes. Both instances need the current version. Connecting instances that run different versions is not supported.

It removes the connector on your instance and on the partner instance. Hooqs rely on their connector to reach the partner instance, so delete a connector in use only on purpose.