Hooq help centre
Glossary
| Term | Meaning |
|---|---|
| Hooq | The app, and also one pair of projects with the rules for syncing them. You can have many Hooqs. |
| Hooqed | A work item that is part of a Hooq and has a partner. |
| Partner | The other work item of a pair. Also called the copy when you look from the original. |
| Source / target project | The two projects of a Hooq. Which is which only matters for the direction of a mapping. |
| Same-instance Hooq | A Hooq between two projects on one Jira Cloud site. |
| Cross-instance Hooq | A Hooq between projects on two different Jira Cloud sites. Needs a connector and approval from the other site. |
| Connector | A trusted link between the Hooq on your site and the Hooq on another site. It must be Active to be used. |
| Active / Pending | Connector states. Pending means saved but not yet activated. |
| Work type | What Jira calls an issue type, for example Bug or Task. |
| Mapping | A rule that matches something in one project to something in the other (a work type, a field value or a status). |
| Correlation | A field mapping that matches the values of two fields one by one, for example drop-down options. |
| Limit Work Items | A JQL condition on the Work Types tab that keeps a Hooq to some work items. |
| JQL | Jira Query Language, Jira's search language. |
| Draft and published | Changes in Configuration are a draft. A Hooq works from the published configuration only. |
| Resync | Sending the current state of work items that already have a copy again. |
| Sync Health | The four numbers at the top of a Hooq: Issues synced, Errors, Last sync, Sync speed. |
| Hooq panel | The Hooq - Work Sync Panel on a work item. |
| Forge | Atlassian's platform that Hooq runs on. It sets some limits, for example the file size between sites. |
Related pages
Want to raise a ticket? Click here (opens in a new tab)