Mortise Apps
JiraIn review
TeamLens for Jira
Makes the native Atlassian Team field reportable and searchable: team reports across projects, a dashboard gadget grouped by team, JQL by team name and a team panel on every issue.
Jira · 2 apps
Apps for Jira Cloud: team reports and dependency graphs
Two apps for Jira Cloud, each closing one gap that teams hit every day. TeamLens makes the native Team field reportable and searchable; LinkLens draws issue links as a dependency graph. Both are built on Atlassian Forge, read data as the person using them and need no configuration to start.
Apps for Jira
The badge shows where each Atlassian Marketplace listing stands.
JiraIn review
LinkLens for Jira
Draws issue links as a dependency graph: every blocker chain in a project on one canvas, circular dependencies in red, and the same chain on each issue.
How these apps handle your data
Built on Atlassian Forge with no external servers and no outbound network access. Data is read as the viewing user, so Jira permissions always apply. TeamLens stores a team directory (ids and names) and LinkLens stores per-project display settings, both inside Atlassian's Forge storage on your site.
Frequently asked questions
About the apps on Jira.
Which Jira products do the apps work with?
Jira Cloud only: Jira Software, Jira Work Management and Jira Service Management, in team-managed and company-managed projects. Jira Data Center is not supported because the apps are built on Forge.
Do the Jira apps send data outside Atlassian?
No. Both run on Atlassian Forge inside Atlassian's infrastructure with no external servers and no outbound network access, and they read issues as the person using them. TeamLens stores only team ids and names, and LinkLens only per-project display settings, in Forge storage on your own site.
Do I need both apps?
No. They are independent. TeamLens is for the Atlassian Team field (reports, a dashboard gadget, teamIn() and noTeam() in JQL); LinkLens is for issue links (a dependency graph of whole blocker chains). Install either one or both.
How are the Jira apps priced?
Free for sites with up to 10 users. Above that, TeamLens is USD 1 per user per month and LinkLens about USD 0.20 per user per month, with volume discounts, billed by Atlassian. Each has a 30-day free trial.
Articles for Jira
Questions teams asked, answered with sources: what Jira does natively, what it does not, and where an app fits.
JiraLinkLens for Jira
How do you see a dependency map in Jira without Premium?
Jira draws dependencies one issue at a time unless you pay for Premium's Plans. What Free and Standard can do, what Plans adds, and where an app fits.
JiraTeamLens for Jira
Team workload in Jira: see each team's open, blocked and overdue work when Jira only reports per assignee or per board
Jira Cloud's Workload Pie Chart, Issue Statistics and board reports never group by the Atlassian Team field. Here is what a per-team workload view needs, how far native Jira gets, and how TeamLens reports it across projects.
JiraTeamLens for Jira
Team velocity in Jira when teams do not match boards: velocity per Atlassian Team across sprints
Jira's Velocity Chart belongs to one board, so a team that works across boards, or a board shared by teams, never gets a true velocity. Here is what velocity per team needs and how TeamLens computes it from the Sprint field.
JiraLinkLens for Jira
How to find Jira issues that are blocked by issues that are still open
issueLinkType = "is blocked by" also returns work whose blocker is done. What JQL cannot do, the Automation fix, and how to see live blocker chains.
JiraTeamLens for Jira
Cross-team dependencies in Jira: a who-waits-on-whom matrix from issue links
Jira records every "is blocked by" link but shows them one issue at a time. Here is how to turn issue links plus the Team field into a cross-team dependency report, what native Jira offers, and how TeamLens builds the matrix.
JiraLinkLens for Jira
See the whole blocker chain in Jira: from a flat list of issue links to a dependency graph
Jira shows issue links one issue at a time. A blocker three hops away stays invisible until it is late. Here is how to see the whole chain.
Other platforms
The same approach, where else your team works.
Confluence
Live Jira team reports and dependency maps in Confluence pages.
monday.com
Every dependency chain on a board as one graph.
Chrome extension
Next platform, in development.
Coming
Questions about the Jira apps: support@mortiseapps.com, reply within one business day. All products →