Logjam for Jira · Unleash Consult
Email support@unleashconsult.io with "Logjam" in the subject line.
Support is by email only, in English or Danish. There is no phone line and no ticket portal.
Please do not send passwords, API tokens or personal data.
These are design decisions rather than faults.
Dependencies come from Jira issue links. If your team does not maintain "blocks" and "is blocked by" links, the dependency table will be empty — and the app says so, rather than letting an empty table imply nothing is blocked.
Only blocking links count. "Relates to" is ignored on purpose; it is noise in this context.
The silence threshold is seven days and is not configurable. The report answers a present-tense question ahead of a weekly meeting. A threshold dial reads like a reporting period but behaves like a tolerance setting — moving it to thirty days does not show a different stretch of time, it just stops calling things stuck.
Epics are excluded from the silence rules. Work on an epic's children does not update the epic itself, so flagging epics as silent would be noise.
Very large projects. The app reads up to 5,000 work items per query. In a larger project the lists show the first 5,000 and do not say that anything was left out.
The full rulebook — every figure and the rule behind it — is on the How it works page.
Jira Cloud. A Jira administrator installs the app; it then appears as a page on the project.
See the privacy policy.