Skip to main content
Limbus LabGet Hooq for Jira (opens the Atlassian Marketplace)
Help centre menu

Release 5.136.0

Production Version 5.136.0 (18 October 2026)

What is new

Prevent Comment Deletion now works

With Prevent Comment Deletion on (the default), the copy of a deleted comment stays. With it off, deleting an original comment deletes its copy, on one instance and between two instances. Deleting a copy never deletes the original. See Comments.

Worklog sync works again, and restricted worklogs stay private

Copying worklogs failed with an error before; it now works. The copy carries the time, the start time, the comment and the visibility of the original. 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, and is otherwise not copied: it is never made public. The modes are now Disabled, Anonymous and Enriched; User-based is gone, and an old User-based setting behaves as Enriched. Edits of an existing worklog are not synced. See Worklogs.

Comment as Hooq copies the plain comment

With Comment as Hooq in the Comments tab the copy no longer starts with the line commented on ... by .... Comment as actual author keeps the line.

Existing comments and worklogs when the Hooq starts

With Limit by Filter and the boxes Sync comments and Sync worklogs ticked and published, Hooq copies the comments and worklogs that the filter’s work items already have when the Hooq starts. Nothing is copied twice. See Work types.

Defaults no longer block a copy

A default for a field that is already mapped no longer stops the copy from being created. A default for a field that is not on the create screen of the receiving project is skipped with a warning. See Defaults.

Attachments and Worklogs show the real state

The label at the top of these tabs shows Working, Stopped or Off as it really is, and Last activity shows when the Hooq last synced.

Troubleshooting filters and the Documentation menu

In the Troubleshooting tab the Error filter (All, Rate limit, Failure) and the Project filter now work. The Documentation item in the header menu opens this help centre. See Troubleshooting.

The Advanced tab saves only your changes

Saving the Advanced tab no longer changes settings you did not touch. See Advanced.

The How it works text of Manual Link now says to leave Limit Work Items empty while you link.

A filter pass ends without a false error

A pass of Limit by Filter no longer ends with the entry Filter sync search failed (400) in the Troubleshooting tab.

Boards: create works, rename is not synced

When a board is created in a mapped project, the partner board is now created (this failed before). Renaming a board is not synced, because Jira’s API cannot rename a board; Board Updated and Configuration Changed only create a missing partner board. Deleting a board honours Prevent Board Deletion: on keeps the partner board, off deletes it. A board delete is not forwarded between instances. See Boards.

Sprint updates reach the partner

Updating a sprint (name, goal, end date) now reaches the partner sprint; it failed before. A sprint created right after you publish Boards and Sprints no longer needs a second save. See Sprints.

Dashboard gadget: honest figures and saved settings

The gadget shows Linked pairs recorded by Hooq, counted from the links Hooq stores, not from a live Jira search; pairs where Hooq saw a delete are left out. Clear returns to All Hooqs, the saved Hooq stays selected after a reload, and the settings form shows the saved values.

The Parent of the copy follows

When a synced work item gets a new Parent, or is created under one, and that parent is synced in the same Hooq, the Parent of the copy follows. See Fields and values.

Comments between instances are not lost on a slow send

A comment written while the other instance is briefly slow, or when the first send times out, is now sent again by the automatic retry. In rare cases this can leave a duplicate copy instead of a missing comment.

Boards and sprints between instances are safer

Sprint, board-delete and sprint-update events can no longer land on a wrong board or sprint when board or sprint numbers on the two instances are the same. A sprint on a board that is not in the Board Scope is skipped. Refresh Boards and the filter dropdown list only boards and filters the Hooq app can see: share a private filter with the project first.

Safer editing of a running Hooq

Edits you have not saved are no longer lost when the page refreshes in the background, on all Configuration tabs. Importing a configuration closes its dialog by itself, and the Draft view stays selected.

Known limitations

  • Only comments that Hooq copied after this release can be deleted by Prevent Comment Deletion. A comment deleted while the Hooq is stopped is not carried over.
  • Edits of an existing worklog are not synced, and a Resync does not send worklogs.
  • A worklog restricted to a project role is not copied when the Hooq user is not a member of that role in the project of the original.
  • A default for a field that is not on the create screen of the receiving project is skipped.
  • Renaming a board is not synced, and a board delete is not forwarded between instances.
  • A sprint copied before the destination board was changed is no longer updated or deleted. With the same project key on both instances, sprint events from the target side are not synced.
  • In rare cases the automatic retry of a comment can leave a duplicate copy instead of a missing comment.
  • A board whose Jira filter is private appears in the lists only after the filter is shared with the project.
  • The Parent of the copy follows only inside one Hooq, and a removed Parent is not cleared on the copy.
  • A comment deleted within a few seconds of being created may keep its copy.
  • With Comment as Hooq, a comment sent from the issue panel also arrives without the author line.
  • If one work item has several worklogs that are identical in start time, time spent and comment, a filter pass between two instances can reduce them to one copy, whatever their age. Worklogs logged live are never skipped this way.

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