Team Statistics gadget
Groups any set of issues by the Atlassian Team field. Use it where Jira's native gadgets (Pie Chart, Issue Statistics, Two Dimensional Filter Statistics) cannot show Team.
Add the gadget
Dashboard, Edit, Add gadget, search Team Statistics, Add. The settings form opens automatically.
Settings
| Setting | Meaning | Example |
|---|---|---|
| JQL filter | Which issues to include. Any valid JQL, including the app's own functions. | project in (ABC, DEF) AND sprint in openSprints() |
| Metric | Issue count or Story points (sums Story point estimate or Story Points). | Story points |
| Refresh | The gadget refreshes every 15 minutes and whenever you reload the dashboard. |
Leave the JQL empty to use resolution = Unresolved.
Reading the table
| Column | Meaning |
|---|---|
| Team | Team name. Issues with no Team appear in a (no team) row so nothing silently disappears. |
| Issues / Story points | The chosen metric for that team. |
| % of total | Share of the whole filter. |
| Members | Current team size from Atlassian Teams. Shown as - if the team could not be looked up. |
Columns Team and value are sortable. The header lozenge shows total issues and total metric.
Tips
- Combine with
teamIn()to compare a handful of teams:issue in teamIn("Payments", "Checkout") AND statusCategory != Done. - Add two copies of the gadget, one with Issue count and one with Story points, to spot teams with many small items.
- Use
project = X AND issue in noTeam()as a hygiene gadget for the RTE or admin.
Limits
- Up to 5,000 issues per gadget. Narrow the JQL if you exceed this; the gadget shows a message.
- Story points require a numeric story points field on the issues. Team-managed projects use Story point estimate; company-managed use Story Points. Both are detected automatically.
Was this page helpful? Email support@mortiseapps.com.