Mortise AppsTeam reports
Last updated 2026-09-28
Five reports grouped by the Atlassian Team field, computed live from one scope of projects. Jira's own reports are per board or per assignee; these are per team, across as many projects as you pick.
| Report | Question it answers |
|---|---|
| Workload | How much open, blocked and overdue work does each team hold right now? |
| Dependencies | Which teams are waiting on which other teams, and which of those blockers are overdue? |
| Velocity | How much does each team complete per sprint, and is that stable, improving or slipping? |
| Aging | Which in-progress work has been sitting in its status the longest, per team? |
| Hygiene | Which open issues have no team, no estimate or no due date, per project? |
Open the reports
- Across projects: top navigation, Apps, TeamLens Team reports. Pick one or more projects and select Run report.
- Inside one project: open the project, select the Team reports tab (under More if the tab bar is full). The project is pre-selected and the report runs automatically. You can add more projects to the scope.
Each report tab has its own URL (/workload, /dependencies, /velocity, /aging, /hygiene), so a link to a specific tab can be bookmarked or pasted into a page.
Scope
| Control | Meaning |
|---|---|
| Projects | One or more projects. Issues are read from all of them together, so a team that works in three projects is one row. |
| Extra JQL (optional) | Any clause, ANDed with the project list. Examples: issuetype != Epic, sprint in openSprints(), issue in teamIn("Checkout Team", "Platform*"). |
Done work is limited to the last 30 days, so "Done" means recently finished, not history. A scope is capped at 3,000 issues; the page tells you when the cap is hit, and narrowing with JQL fixes it.
Nothing is stored. Every run reads Jira as you, so you see exactly the issues your permissions allow.
Workload
Summary tiles: teams, open issues, blocked, overdue and open story points for the whole scope.
The chart stacks To do, In progress and Done (30d) per team; the toggle switches it to story points.
| Column | Meaning |
|---|---|
| Team | Team name. Issues with no team appear in a (no team) row at the bottom so nothing is hidden. |
| Members | Current team size from Atlassian Teams (- if the team could not be looked up). |
| To do / In progress / Done (30d) | Issue counts by status category. Done counts issues resolved in the last 30 days. |
| Blocked | Open issues that are flagged in Jira, or whose status name contains "block". |
| Overdue | Open issues whose due date has passed. |
| Open points | Story points on To do and In progress issues. |
| Issues | Opens the team's open issues below the table: key, summary, type, status, points, due date, blocked marker. |
Dependencies
A dependency is an unresolved issue link between two issues that belong to different teams. Links inside one team are ignored, and resolved blockers are dropped.
| Control | Meaning |
|---|---|
| Link type | Which link type counts. Blocks is selected by default when it exists; All link types includes every directional link. |
Sections:
- Who waits on whom. Rows wait on columns. A number is how many unresolved issues of the column team block the row team; an overdue lozenge shows how many of those are past due.
- Per team. Waiting on other teams, blocking other teams, and overdue blockers the team owns.
- Dependencies, overdue first. Every pair: waiting issue and team, the relationship, blocking issue and team, blocker status and due date. Overdue means the blocker or the waiting issue is past its due date; Due soon means the waiting issue is due within 7 days.
Issues outside the scope that are linked to issues inside it are looked up (up to 400) so their team is known. Add their projects to the scope for a complete picture.
For the full chain drawn as a graph, see LinkLens for Jira.
Velocity
Per team, per closed sprint, computed from each issue's Sprint field history. No board configuration is needed and sprints from several boards are combined.
| Control | Meaning |
|---|---|
| Range | Last 4, 6, 8, 10 or 12 closed sprints (default 6), newest last. Sprints closed in the last 12 months are considered. |
| Story points toggle | Points or issue counts. |
| Column | Meaning |
|---|---|
| Avg points (or issues) / sprint | Average completed over the sprints in which the team had work. |
| Last sprint | Completed in the most recent sprint. |
| Trend | Improving if the last sprint is at least 10% above the average of the earlier sprints, Slipping if at least 10% below, otherwise Stable. |
| Completed / committed | Predictability over the range. Below 70% is marked over-committed. |
| One column per sprint | completed / committed for that sprint. |
Definitions: Committed = issues in the sprint when it closed, including items carried over from an earlier sprint. Completed = resolved by the sprint's close. Carried over = the rest. The chart "Completed per sprint, by team" plots the series; "Completed vs carried over" shows one team's bars.
Aging
Only In Progress issues are counted. Age = days since the issue entered its current status category (Jira's statusCategoryChangedDate), so an issue moved to In Progress today shows 0.
| Control | Meaning |
|---|---|
| Stale after | 7, 14, 21 or 30 days. |
| Column | Meaning |
|---|---|
| In progress | Count of in-progress issues for the team. |
| Avg days in status | Mean age. |
| Oldest (days) | The single oldest issue. |
| < 3 days, 3-7 days, 7-N days, N+ days | Age buckets; the last bucket is the stale count. |
Below the table, Stale work, oldest first lists every stale issue with its team and age.
Hygiene
Per project in the scope, for open issues only.
| Column | Meaning |
|---|---|
| Open issues | Unresolved issues in the project. |
| No team / % without team | Issues with an empty Team field. |
| No estimate | Stories, tasks and bugs with no story points (shown only if a points field exists). |
| No due date | Issues without a due date. |
| Fix it with JQL | Paste-ready project = X AND issue in noTeam() AND statusCategory != Done. |
The list below shows the open issues with no team. Put the JQL in a scheduled Automation rule that notifies the project lead and unowned work stops piling up.
Tips
- Add all the projects one team touches so its workload and velocity are complete, then use
issue in teamIn("Team Name")in the JQL box to focus on that team. - For a release view, add
fixVersion = "2026.10"to the JQL and read Workload and Dependencies together. - Bookmark the Dependencies tab URL for the weekly cross-team sync; overdue blockers are always on top.
- Use Velocity with story points where estimates exist and issue counts where they do not; both are honest.
Limits
- 3,000 issues per scope, 400 linked issues outside the scope, 300 issues in a team's drill-down list, 300 rows in the dependency list. Narrow the scope with JQL when a report reports a cap.
- Velocity does not model scope added or removed mid-sprint; it credits what was in the sprint at close.
- Velocity needs Jira Software sprints. Business and Service Management projects show the other four reports only.
- Reports are computed on demand and are not cached; a very large scope can take several seconds.
Was this page helpful? Email support@mortiseapps.com.