← Back to Documentation

User Documentation

Version 1.0 · Last updated January 2026 · Platform: Atlassian Forge (Jira Cloud)

Overview

SprintINSite is a Forge-powered Jira app that provides real-time sprint capacity tracking, baseline monitoring, and team workload visibility. It helps Scrum teams understand their sprint progress, track scope changes, and monitor individual contributions.

Key Features

• Sprint Timeline — Visual progress bar showing time elapsed in the current sprint
• KPI Dashboard — At-a-glance metrics for Issues, Points, Scope, and Velocity
• Baseline Tracking — Monitors scope changes (additions and removals) throughout the sprint
• Team Capacity — Individual breakdown of points, progress, and status per team member
• Velocity Indicator — Smart "On Track" / "Behind Schedule" status based on progress vs time
• Status Breakdown — Points categorised by Done, In Progress, and To Do

Getting Started

Before using SprintINSite, make sure you have:

• A Jira Cloud instance (team-managed or company-managed)
• A Scrum board with an active sprint
• Issues with Story Points assigned
• Project access permissions

To access the app, navigate to your Jira project and look for "Jira Points Tracker 1" in the project navigation tabs. Click it to open the Sprint Capacity Snapshot dashboard.

For a quick walkthrough, see the Quick Start Guide.

Dashboard Components

Header Section

The header displays the app title ("Sprint Capacity Snapshot"), along with badges showing your Jira project key, Scrum board name, and the current active sprint name. A Refresh button lets you manually reload data at any time.

Sprint Timeline

Shows the sprint duration with a visual progress indicator including the date range (start and end dates), a colour-coded "days remaining" badge, and a progress bar representing time elapsed.

The colour coding works as follows: Green means more than 7 days remaining, Yellow means 3 to 7 days remaining, and Red means fewer than 3 days remaining.

KPI Cards

Four key metrics are displayed in card format across the top of the dashboard:

• ISSUES — Total number of issues in the sprint
• TOTAL POINTS — Sum of all story points
• SCOPE — Baseline to current points, tracking any scope creep (e.g. "18 → 21")
• VELOCITY — Points completed out of total points, with a status indicator

Velocity status indicators: On Track (green) when completion percentage is at or above time elapsed percentage, Slightly Behind (yellow) when within 15% of the target, and Behind Schedule (red) when more than 15% behind target.

Sprint Completion

A detailed view of overall sprint progress, including a visual progress bar, a count of points done out of total, and a status breakdown showing points in each category: Done, In Progress, and To Do.

Baseline Tracking

The baseline system captures a snapshot of your sprint the first time the app is loaded for a given sprint. It then tracks changes against that baseline, including points added after sprint start, points removed after sprint start, and per-person scope changes.

When you first view a sprint, you'll see a "Baseline Captured" message. On subsequent visits, a "Baseline Active" message confirms that scope changes are being tracked.

Team Capacity

Individual cards are shown for each team member, including:

• Header — Team member's display name, sprint share percentage, and total points assigned
• Progress — Personal completion bar and count of points done vs assigned
• Baseline — Points at baseline vs current, with Added/Removed badges if scope changed
• Status Breakdown — Mini cards showing points in each status category with percentages
• Workflow Detail — Top 5 workflow statuses with point counts

Understanding the Metrics

Story Points Detection

The app automatically detects your Story Points field by searching for common field names: "Story point estimate", "Story Points", "Story points", and "Story point". The detected field ID is cached for performance.

Scope Change Calculation

Added Points are points in the current sprint that were not in the baseline. Removed Points are points that were in the baseline but are no longer in the sprint. Scope Change is calculated as End Total minus Start Total.

Velocity Calculation

Velocity status compares the percentage of points completed against the percentage of time elapsed in the sprint. If done percentage is at or above time percentage, the status is "On Track". If done percentage is within 15 points of time percentage, it is "Slightly Behind". If done percentage is more than 15 points below time percentage, it is "Behind Schedule".

Common Use Cases

• Daily Standup — Use the Sprint Completion section to assess whether you're on track, how much is in progress vs blocked, and who has capacity.
• Sprint Planning — Review the baseline after planning to capture initial scope. Any subsequent changes will be tracked automatically.
• Sprint Review — Compare baseline to final state to see what was added mid-sprint, what was removed, and who delivered the most points.
• Capacity Planning — Use Team Capacity to understand workload distribution, individual completion rates, and unassigned work.

Troubleshooting

"No Scrum-capable board found"

The app requires a Scrum board (not Kanban). Make sure you have a Scrum board in the project and open the app from within the Scrum board context.

"No active sprint found"

No sprint is currently active. Go to your Backlog, start a sprint, then return to the app.

"Error loading data"

This is typically a network or permission issue. Click Refresh to retry, check that you have project access, and verify the board has issues with story points assigned.

Data Not Updating

If you're seeing stale data, click the Refresh button in the app. If that doesn't help, hard refresh your browser (Cmd+Shift+R on Mac, Ctrl+Shift+R on Windows).

Technical Details

• Supported boards: Company-managed Scrum boards (type "scrum") and Team-managed Scrum boards (type "simple"). Kanban boards are not supported.
• Data storage: Baselines are stored using the Forge Storage API, scoped per project and sprint. Baselines persist until the sprint changes.
• Permissions: The app uses read-only permissions only — it reads issues, projects, boards, sprints, and user information, and stores baseline data. It does not create, modify, or delete any Jira data.

Frequently Asked Questions

Does it work with Kanban boards?
No, the app requires Scrum boards with sprints.

Can I reset the baseline?
Currently, baselines reset automatically when a new sprint starts. Manual reset is not yet available.

Why are some issues showing as "Unassigned"?
Issues without an assignee are grouped under "Unassigned" in the Team Capacity section.

Does it support sub-tasks?
Yes, all issues in the sprint are included regardless of issue type.

How often does the data refresh?
Data is fetched on page load and when you click Refresh. There is no auto-refresh.

Support & Feedback

For issues, feature requests, or feedback, contact us at support@sprintinsite.com.

Changelog

Version 1.0 (January 2026) — Initial release with sprint capacity tracking, baseline scope monitoring, team workload breakdown, velocity tracking with smart indicators, and progress bars for timeline and completion.