Sprint Subtask Pulse user guide

What Sprint Subtask Pulse does

Sprint Subtask Pulse is a read-only Jira Cloud project page for Scrum work. It shows the current, visible subtask progress for a selected active or completed sprint, grouped under parent issues. It is designed to make unfinished subtask work easy to find during sprint review, stand-up, and delivery triage.

The report shows:

• Overall percentage and count of current visible subtasks for the selected sprint’s parents
• Done, in-progress, to-do, and other/unknown status-category counts
• Parent issues ordered by unfinished subtask work
• Expandable subtasks with issue links, summaries, assignees, and current statuses
• Parents returned by Jira with no visible subtasks, disclosed separately

Sprint Subtask Pulse is being prepared for Atlassian Marketplace. Once available:

Install and open the report

1. Install the app on a Jira Cloud site with a Scrum board or project where you have access to the relevant issues.
2. Open the Jira project page containing Sprint Subtask Pulse.
3. Select an active or completed sprint.
4. Expand a parent to inspect its visible subtasks.

The app is read-only. It does not edit issues, statuses, assignees, sprints, or estimates.

How calculations work

Completion is the number of visible subtasks in Jira's Done status category divided by the total number of visible subtasks included in the report. Status categories are used instead of English status names, so custom workflows can be represented. Statuses that do not map to Jira's To Do, In Progress, or Done categories are counted as Other and are not treated as done.

The app retrieves visible sprint issues, then adds current direct subtasks for the visible non-subtask issue keys and merges duplicates. If the sprint endpoint itself returns a subtask without its parent, that subtask can still appear. The report states this condition when it occurs.

Completed sprints show the current visible Jira issue data when the report is opened or refreshed. They are not historical snapshots, and the app does not reconstruct what the sprint looked like at its close.

Permissions and restricted issues

Requests run in the signed-in user's Jira context. Jira browse permissions and issue security determine which issues are returned. Two users can therefore see different totals for the same sprint. The report discloses that its results reflect only work the current user can view.

Current product boundaries

• Jira Cloud only
• Scrum sprints; a Kanban context does not provide the required sprint workflow
• Direct subtasks grouped under their immediate parent
• Read-only current-data report
• No time estimates, time tracking, story points, notifications, exports, charts, AI, or external database

Troubleshooting

No sprint is available

Open the report from a Jira project/board with accessible active or completed Scrum sprints and confirm that your Jira permissions allow you to view them.

No subtasks are shown

Jira may have returned visible parent issues without visible subtasks. The report excludes parents without subtasks from completion math and explains this state. Check issue visibility and the selected sprint.

Totals do not match another user

Compare Jira browse permissions and issue-security settings. The app intentionally calculates from each user's visible data.

The report fails to load

Select Try again or Refresh where offered. If the sprint list or project context fails to load, select Try again on the error message. Reload the page if retry does not recover it. For support, send the Jira site URL, board/project context, sprint name or ID, approximate time including timezone, and visible error text. Do not send passwords, tokens, session cookies, or confidential issue content.

License required

The commercial candidate requires an active Marketplace license when Forge supplies license metadata. Ask your Jira site administrator to check the trial or subscription if the license message appears.