Release 5.143.0

Production Version 5.143.0 (21 November 2026)

This is a security release. Nothing changes in how Hooqs sync, and nothing needs to be reconnected or approved again.

What is new

Messages are accepted only from the paired partner

A Hooq between two Jira sites now accepts messages only through its own connector, from the partner site it was paired with. A message that names a different site is refused, and nothing is written.

Each signed request can be used only once

Connect and delete requests between sites can no longer be sent again by someone who copied them. A repeated request is refused. Used request codes are cleaned up automatically.

Connector secrets are kept in protected storage

The secrets that sign messages between the two sites now live in the platform's protected secret store.

Stricter checks before anything is saved

Hooq checks every part of an incoming request before it saves anything. Requests that are not signed get the same short answer every time, and nothing is stored for them. Addresses and fields that a partner sends are checked more strictly.

Clearer messages for admins

  • If the partner site cannot confirm that a connector was deleted on its side, the admin now sees a warning that says so.
  • A refused Reconnect shows a short, general reason.

Good to know

  • For up to 5 minutes after you click Reconnect, a message from the partner site can be refused with "invalid signature", and a comment sent in that time can be missed. This is not new in this release, and a fix is planned.
  • If the partner site answers "too many requests" while a comment is being copied, that comment can be missed. This is not new in this release.

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