Monolyn Labs
Docs

Sprint Canvas Documentation

Last updated: 2026-03-13
Official product docs for customers and Atlassian Marketplace review.
Start here: Overview · Guide · Marketplace · Support · Privacy Policy · Security Policy · Terms / EULA

Sprint Canvas for Jira (Capacity Planning) is an Atlassian Forge app by Monolyn Labs. It adds a Capacity page to Jira projects and helps teams compare sprint demand versus capacity for the next three sprints.

What Sprint Canvas does

  • adds a project page named Capacity inside Jira
  • uses a selected Jira Software Scrum board for calculations
  • loads the next 3 sprints (active plus future)
  • calculates demand, capacity, delta, utilization, and health
  • supports a default weekly capacity per person and optional per-person overrides
  • shows data quality badges when work is unestimated, unassigned, truncated, or when board estimation cannot be read

Prerequisites

  • Jira Cloud with Jira Software access
  • a Scrum board associated with the target project
  • board estimation configured to use Story Points or a time-based estimate field
  • issues in the target sprints should be assigned and estimated for the strongest signal
  • the app must be installed and the user must have permission to view the project and board data

How to open Sprint Canvas in Jira

  1. Open the Jira project where Sprint Canvas is installed.
  2. In the project navigation, open Capacity.
  3. If no board is selected yet, open Settings.
  4. Select the Scrum board Sprint Canvas should use.
  5. The app then loads the next three sprints automatically.

Configuration

1) Select a Scrum board

Sprint Canvas reads the project’s available Scrum boards. Pick the board that represents the sprint plan for the project.

2) Set the default capacity per person

Set a weekly capacity value for each person. The initial default is 20. This value is applied per person, per week, and Sprint Canvas scales it by sprint length.

3) Optional per-person overrides

If one team member has a different available capacity, add an override for that person. Overrides appear after Sprint Canvas detects assignees in the upcoming sprints.

4) Auto-save behavior

Settings are saved automatically. You do not need a separate save button inside the app UI.

How calculations work

  • Demand: Sprint Canvas sums the estimation field used by the selected board. If the board uses a time-based field, the app converts stored seconds into hours for display.
  • Capacity: Sprint Canvas uses the detected assignees in the sprint, multiplies each person’s weekly capacity by the sprint length in weeks, and applies any configured overrides.
  • Delta: Capacity minus demand.
  • Utilization: Demand divided by capacity.
  • Unit detection: the app automatically uses the board’s estimation method, so the unit is derived from Jira configuration rather than manually chosen inside the app.

How to interpret health and signals

  • OK: utilization is below 85%.
  • Tight: utilization is 85% to 100%.
  • Overbooked: utilization is above 100%.
  • No signal: Sprint Canvas cannot derive usable capacity, usually because there are no assigned issues, no assignees detected, or capacity cannot be calculated.
  • No capacity: demand exists but derived capacity is zero.
  • Counts: the board estimation method could not be read, so Sprint Canvas falls back to issue counts instead of numeric demand.

Data quality badges may appear for:

  • No estimation
  • Unestimated issues
  • Unassigned issues
  • Board config error
  • Truncated results when a very large sprint hits a safety limit

How to test on a fresh Jira project

  1. Create or use a Jira Software project with a Scrum board.
  2. Create one active sprint and one or two future sprints.
  3. Add several issues to those sprints.
  4. Assign issues to team members.
  5. Add estimates to the issues using the board’s configured estimation method.
  6. Open the project’s Capacity page.
  7. Select the Scrum board in Settings.
  8. Set the default weekly capacity and any test overrides.
  9. Verify that the app shows Current sprint, Health, and Canvas data for the next three sprints.
  10. Check that utilization, delta, and health change when you add or remove estimates, assignments, or overrides.

Troubleshooting

No Scrum boards found

Sprint Canvas requires a Jira Software Scrum board in the project. Create a Scrum board or confirm that the current user can access the board.

Health shows “No signal”

Common causes are: no sprint issues, unassigned issues, unestimated issues, or missing estimation configuration on the board.

Health shows “Counts”

This means Sprint Canvas could not read a usable estimation method from the board configuration. Configure Story Points or a time-based estimate field on the board.

Utilization is blank or missing

Confirm that the sprint has estimates, at least one detected assignee, and a valid capacity setting.

The app errors after a scope change or upgrade

If app scopes changed, Jira may require a re-consent or upgrade cycle. In that case, run forge install --upgrade for the relevant environment and site.

Data, privacy, and storage

Sprint Canvas stores only project-level configuration in Atlassian Forge Storage, such as the selected board id, board name, default weekly capacity, and per-person overrides.

  • It does not persist issue descriptions, comments, or attachments.
  • It does not send Jira data to third-party external services.
  • It uses Atlassian Forge and Jira APIs for the app’s functionality inside Jira Cloud.

See the full Privacy Policy for details.

Uninstall and data deletion

  • Uninstall the app in Jira to stop further access.
  • To request deletion of stored configuration, email support@monolyn.nl.

Support and policy links