JiraIn reviewTeamLens for Jira
TeamLens is a Jira Cloud app that adds team reports, dashboard gadgets and JQL functions for the native Atlassian Team field. It is built for Jira admins, RTEs and engineering managers who roll out Plans and Teams and then find that Jira reports per board or per assignee, never per team.
Five reports grouped by team across any projects: workload, cross-team dependencies, velocity, aging and hygiene. Plus a dashboard gadget grouped by team, search by team name with teamIn(), and unowned work with noTeam().
The short version for admins and procurement.
Atlassian asks every Plans customer to use the native Team field, then leaves it unsupported in the places managers look.
Pie Chart, Issue Statistics and Two Dimensional Filter Statistics cannot group by Team. Atlassian ticket JRACLOUD-87808 has been open since 2020 with 600+ votes.
JQL needs the team's UUID: "Team[Team]" = 36885b3c-1bf0-…. Nobody remembers that, and JQL cannot ORDER BY Team at all.
Issues with no team vanish from team views. There is no built-in "no team" report, so nothing catches them.
Mirror the Team into a select-list custom field with Automation, then keep it in sync forever. Admins call it "very load heavy".
Five focused capabilities. Nothing is written to your issues.
Pick one or more projects and get five reports grouped by team, read live as you: Workload (to do, in progress, done, blocked, overdue, open points, drill-down), Dependencies (a who-waits-on-whom matrix from issue links, overdue blockers first), Velocity (completed and committed per team per sprint across every board, average, trend, predictability), Aging (days in status for in-progress work, stale list) and Hygiene (no team, no estimate, no due date, with paste-ready JQL). Every tab has its own URL.
Mortise AppsProject → Team reports or Apps → TeamLens Team reportsThe Dependencies report keeps only the unresolved links whose two ends belong to different teams, so intra-team links do not add noise. Rows wait on columns, overdue blockers are flagged in the cell, and the list below is sorted overdue first. Pick the link type; Blocks is the default.
Jira's Velocity Chart belongs to one board. TeamLens computes committed, completed and carried-over work per team from each issue's Sprint history, across every board in the scope, for the last 4 to 12 closed sprints. Average, last sprint, trend and completed-over-committed per team.
Any JQL, grouped by Team. Count issues or sum story points, see each team's share and size, and get an explicit (no team) row so nothing silently disappears.
project = SHOP AND sprint in openSprints()
Search by team name, case-insensitive, with a trailing wildcard. Works in filters, boards, JSM queues and Automation.
issue in teamIn("Checkout Team", "Platform*")
issue not in teamIn("Checkout Team")
Find every issue that no team owns. Pair it with a scheduled Automation rule and the backlog stays clean.
issue in noTeam() AND statusCategory != Done
A panel showing the assigned team's description and size, with a link to the team profile.
Three steps, no configuration screens.
Select Get it now on the TeamLens listing and choose your Jira Cloud site. Jira admin rights are required; nothing needs configuring.
In any project select the Team reports tab, or go to Apps, TeamLens Team reports and pick several projects. Workload, Dependencies, Velocity, Aging and Hygiene are computed per team from that scope.
Edit any dashboard, add the TeamLens Team Statistics gadget, enter a JQL filter such as project = ABC AND resolution = Unresolved, and pick issue count or story points.
In any filter, board or queue use issue in teamIn("Team Name") or issue in noTeam() to find work with no team.
What changes once TeamLens is installed.
| Capability | Native Jira Cloud | With TeamLens |
|---|---|---|
| Workload per team across projects | Per assignee or per board only | Workload report |
| Cross-team dependencies in one view | Open each issue | Who-waits-on-whom matrix |
| Velocity per team | Per board only | Velocity report, across boards |
| Aging work in progress by team | Control chart per board | Aging report |
| Group a dashboard gadget by Team | No | Yes |
| Sum story points per Team | No | Yes |
| JQL by team name | UUID only | teamIn("Name") |
| Wildcard team search | No | teamIn("Platform*") |
| Find issues with no Team | "Team[Team]" is EMPTY | noTeam() |
| Team description and size on the issue | Hover only | Panel |
| Read team member lists | Admin UI only | Not available to apps' own auth (human API token only; JRACLOUD-92072) |
Reviews come from the Atlassian Marketplace listing. We never write our own.
Billed by Atlassian on your Jira invoice. Cancel any time from Jira administration.
Sites with up to 10 Jira users. Every feature included.
Volume discounts apply automatically. 30-day free trial. Roughly $50 for a 50-user site, about $275 for 500 users.
TeamLens fixes a gap Atlassian should close. We price it so it is never the first app cut from a budget, and Runs on Atlassian keeps our costs low.
Straight answers, including what the app cannot do.
Jira's native gadgets (Pie Chart, Issue Statistics, Two Dimensional Filter Statistics) do not list the Atlassian Team field as a statistic type, and JQL cannot order by it. Atlassian tracks this as JRACLOUD-87808 and JRACLOUD-87800, open since 2020. TeamLens adds a Team Statistics gadget that groups any JQL filter by team.
Install TeamLens and use issue in teamIn("Team Name"). Native JQL requires the team's UUID. teamIn() resolves names, including a trailing * wildcard, and supports not in.
Use issue in noTeam(). Combine with statusCategory != Done to see only open work that no team owns.
Open a project's Team reports tab, or Apps, TeamLens Team reports for several projects. The Workload report shows per Atlassian Team the To do, In progress and recently Done counts, blocked and overdue issues, open story points and team size, with a drill-down to the issues. Jira's native gadgets group by assignee, not by team.
The Dependencies report reads the issue links in your scope and keeps the ones whose two ends belong to different teams: a who-waits-on-whom matrix, per-team waiting and blocking counts, and a list with overdue blockers first. Pick the link type; Blocks is the default.
Jira's Velocity Chart is per board and does not know which team did the work. The TeamLens Velocity report groups completed and committed work by the Team field across every board in the scope over the last 4 to 12 closed sprints, with the average, trend and completed-over-committed per team. It is computed from each issue's Sprint field, so it needs no board setup but does not model mid-sprint scope changes.
Yes. Plans writes the same native Team field that TeamLens reads, so the gadget and JQL functions reflect your Plan's team assignments.
Yes. teamIn() and noTeam() work in queue JQL. A myTeams() function for per-agent queues is planned and depends on an Atlassian API change.
Not yet. Atlassian's Teams REST API returns team members only to a human's API token (basic auth, organization scope); it is not available to an app's own Forge or Connect auth context, so no Marketplace app can read member lists on its own (app access is tracked as JRACLOUD-92072). TeamLens shows team size. Member-level features ship when apps can call that API.
No. TeamLens runs entirely on Atlassian's Forge platform with no external servers. It stores only a team directory (team ids and names) in Atlassian's Forge storage for the teamIn() JQL function, and reads issues as the person viewing them, so Jira permissions are always respected.
Free for sites with up to 10 users. Above that, USD 1 per user per month with volume discounts, billed by Atlassian with your Jira subscription. A 30-day free trial starts automatically.
Jira Cloud: Jira Software, Jira Work Management and Jira Service Management, in both team-managed and company-managed projects. It is not available for Jira Data Center.
Known limitation. Apps cannot read Atlassian Team membership from their own auth context yet (the Teams API answers only a human's API token). We publish exactly what that blocks on the limitations page and will ship member-level features the day Atlassian opens the API.
Also for Confluence
The same five team reports, grouped by the Atlassian Team field, as a live macro in any Confluence page: workload, aging, hygiene, velocity and dependencies. It connects to Jira itself, so TeamLens for Jira is not required.
Real problems from Jira teams, worked through with sources.
JiraTeamLens for Jira
Jira has swimlanes per assignee, epic or space, but none per team. Query swimlanes fill the gap: one JQL lane per Atlassian team. The menu path, the clauses, who can do it and the limits. Checked 8 Nov 2026.
JiraTeamLens for Jira
A board quick filter is a JQL clause, and the Team field's JQL compares team ids, not names. How to find the id, the clause to paste, who can add it, and a name-based version. Checked 3 Nov 2026.
JiraTeamLens for Jira
The Atlassian Team field takes a team id, not a name. How to find the field's customfield id and the team id, the Edit issue body that sets it, why sub-tasks cannot have their own team, and the JQL to check the result. Checked 29 Oct 2026.
JiraTeamLens for Jira
The Atlassian Team field is not on every Jira layout by default. Where to add it in company-managed and team-managed spaces, the permission it needs, the 15-team limit for linked teams, and why workflows need the Team UUID. Checked 22 Oct 2026.
Free for 10 users. Installs in under a minute. Runs on Atlassian.
Get TeamLens on the Atlassian Marketplace