LinkLens for Confluence
LinkLens for Confluence is a Confluence Cloud app that draws Jira issue links as a live dependency graph inside a Confluence page. It is built for release managers, delivery leads and product managers whose release pages and cross-team plans live in Confluence while the dependencies live in Jira.
Pick a link type such as blocks / is blocked by and a project or JQL scope. Every chain is drawn left to right, blockers first, read live from Jira as the viewer. Loops are drawn in red, other projects stay in view as dimmed cards, and the whole graph exports as a PNG.
The short version for admins and procurement.
Dependencies live in Jira as a flat list of links on each issue. The pages where releases are planned live in Confluence.
Jira shows "blocks SHOP-4" on one issue at a time. What SHOP-4 blocks next, and what blocks the blocker, takes a trail of open tabs.
A dependency diagram pasted into a release page is wrong the moment someone adds or resolves a link.
Diagramming tools need every box and arrow redrawn whenever Jira changes. Nobody keeps that up past the second week.
A blocks B, B blocks C, C blocks A: nothing can start and Jira does not warn when the loop is created.
One macro, one link type at a time. Nothing is written to Jira or to your pages.
Pick a link type and a project or JQL scope. Every chain is drawn left to right, blockers first, separate chains stacked largest first. Issues without a link of that type are counted, not drawn, so the picture stays readable.
Mortise Appsproject = SHOP AND fixVersion = 2.4Circular dependencies get a red dashed closing arrow and are listed by key under the graph. Issues linked from outside the scope, such as another team's project, appear as dimmed cards so an external blocker never hides. Widen the scope to follow their links too.
Choose a link type (Blocks is the default, any custom type works), Jira projects with optional extra JQL or any JQL query, Hide Done issues, a graph height and an optional title. Several graphs can sit on one page, one per release or per link type.
Hover a card and its full upstream and downstream chain lights up while the rest fades. Click to pin its details, double-click to open the issue in Jira, Find key to centre on any issue.
The whole graph, not only the visible part, at double resolution on white with a legend. The image is generated in the browser and never uploaded.
Hide Done to focus on live blockers, four graph heights, a custom title, dark mode, and a header with issue, chain, link and outside-scope counts.
Three steps and one short configuration panel.
Install the app on your Confluence Cloud site. Confluence admin rights are required.
A site admin connects the app to Jira once, from Manage apps. There is nothing extra to buy and no separate Jira app to install; until then the macro shows Connect LinkLens to Jira.
Edit a page, type /LinkLens and pick LinkLens dependency graph. Choose a link type, a scope (Jira projects or JQL) and optionally Hide Done issues, select Save, then publish. The graph loads live whenever someone opens the page.
What changes once LinkLens is on your Confluence site.
| Capability | Native Confluence | With LinkLens |
|---|---|---|
| Jira dependencies in a page | Jira Issues macro: an issue list | A graph with direction |
| Whole chain, first blocker to last blocked | No | Yes, left to right |
| One link type, both directions | No | Yes, in one pick |
| Circular dependencies | No | Red arrow plus a list |
| Blockers in other projects | No | Dimmed outside-scope cards |
| Stays current when links change | Pasted diagrams do not | Live on every page view |
| Export an image | Screenshot | PNG with legend |
| Create or edit links | In Jira | In Jira (the app is read-only) |
Free for up to 10 users; paid tiers billed by Atlassian on your subscription invoice.
Sites with up to 10 users. Every feature included.
Paid tiers above 10 users, billed by Atlassian. Final rates will be published on the Atlassian Marketplace listing, priced in line with LinkLens for Jira.
Runs on Atlassian keeps our costs low, and every limitation is published before you install. Questions about pricing: support@mortiseapps.com.
Straight answers, including what the app cannot do.
LinkLens for Confluence is a Confluence Cloud app that draws Jira issue links as a live dependency graph inside a Confluence page: every chain of one link type across a project or JQL scope, with circular dependencies in red and PNG export.
No. LinkLens for Confluence connects to Jira itself. LinkLens for Jira is a separate app that adds a Dependencies page and an issue panel inside Jira; the two work independently.
Edit the page, type /LinkLens and pick LinkLens dependency graph. Choose a link type (Blocks is the default), a scope (Jira projects or a JQL query) and optionally Hide Done issues, then Save and publish. A site admin connects the app to Jira on the same site once.
Live. It loads when the page opens and Refresh reloads it. Use PNG export for a point-in-time image.
The one whose outward label means must happen first. Blocks is the usual choice. For a custom type such as Depends on, check which label is outward; if arrows look reversed, the type is defined the other way round.
Yes. Issues outside the scope that are linked to issues in it appear as dimmed, dashed cards. Their own links are not followed; widen the scope, for example project in (SHOP, PLAT), to include them.
No. The app runs on Atlassian Forge with one read-only scope (read:jira-work), no storage, no backend functions and no external network access. PNG export is generated in the browser and never uploaded.
Free for sites with up to 10 users. Larger sites pay a per-user price in paid tiers, billed by Atlassian; the exact rates will be published on the Atlassian Marketplace listing.
Not yet. Use PNG export and paste the image where a static copy is needed.
Known limitations. Read-only, same-site Jira only, one link type per macro, up to 2,000 issues per graph, and outside-scope issues are followed one hop. Everything else is on the limitations page.
Also for Jira
A Dependencies page in every project and a Dependency chain panel on every issue, inside Jira. A separate app on the Atlassian Marketplace; it works on its own or alongside LinkLens for Confluence.
Real problems from Jira teams, worked through with sources.
LinkLens for ConfluenceConfluence can list Jira issues and embed timelines, but not draw blocker chains from issue links. The native options, why hand-drawn diagrams go stale, and a live graph macro.
Free for 10 users. Runs on Atlassian. Nothing to store, nothing leaves your site.