OVERALL RATINGS
INSTALLS
2
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appSee what's blocking your Jira project, and who to ask about it
One task stuck, four waiting behind it
Each blocker lists the work waiting behind it, with that work's deadline when it is overdue or due within a week.
The work that went quiet
Overdue, due within a week, or in progress — and untouched for seven days. Each row says why it was flagged and how many days it has been silent.
Data freshness, stated up front
The share of in-progress work updated in the last seven days — one number telling you how much of the rest to believe.
More details
Nobody opens Jira the day before a status meeting and immediately knows what is stuck. You know roughly what the team is doing. You do not know which task has quietly stopped moving, which one is holding up three others, or who to ask.
Logjam reads your work items and the links between them and answers exactly that: what needs chasing, and what to unblock. Every key is a link. Every blocker names its owner. If it is not in Jira, Logjam does not claim it.
Dependencies come from Jira issue links. Where a team maintains them, Logjam shows every blocker and the work waiting behind it. Where nobody does, it says so — rather than showing an empty table and letting you assume all is well.
Runs on Atlassian. Nothing is stored outside your site and nothing is sent anywhere. Your data never leaves Atlassian.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Logjam for Jira integrates with your Atlassian app
Version information
Version 3.1.0•for Jira Cloud
- Release date
- Oct 9th 2026
- Summary
- Updated Forge libraries and tighter error logging
- Details
Updates Atlassian’s Forge libraries and logs only the error message when a Jira request fails. Nothing changes in what the report shows.
Known limits in this version:
- Blocking dependencies are recognised by finding the word “block” in the issue link type’s name. A link type that has been renamed, or translated into another language, is not picked up.
- The report 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 seven-day window is fixed and cannot be changed.
- Epics are left out of the silence rules, because work on an epic’s children does not update the epic.
Full rules behind every figure: https://unleashconsult.github.io/logjam/how-it-works/
- Payment model
- Paid via Atlassian
- License type
- Commercial