Monolyn Labs
Support

Support — Sprint Canvas for Jira (Capacity Planning)

Last updated: 2026-02-28
Support email: support@monolyn.nl
Support phone: +31 653707921
Support hours: Mon–Fri, 10:00–18:00 CET/CEST
Primary channel: Email is the primary support channel. Phone is available for urgent issues.

New here? Start with the Sprint Canvas overview or the step-by-step guide: How to do sprint capacity planning in Jira Cloud without spreadsheets.

Please avoid sending secrets, production credentials, or sensitive personal data in email.

Service targets

  • P1 critical outage: the app is unavailable or materially unusable for most users. Initial response target: within 1 business day.
  • P2 major issue: a core workflow is impaired but a workaround may exist. Initial response target: within 2 business days.
  • P3 general question or minor issue: informational questions, low-impact defects, or enhancement requests. Initial response target: within 3 business days.

Security vulnerability handling

Security reports should be sent to security@monolyn.nl. For cloud security vulnerabilities affecting Sprint Canvas, Monolyn Labs follows the Atlassian Marketplace Security Bug Fix Policy remediation timelines for cloud apps.

  • Critical (CVSS 9.0 and above): targeted remediation within 4 weeks of report or triage.
  • High (CVSS 7.0 and above): targeted remediation within 6 weeks of report or triage.
  • Medium (CVSS 4.0 and above): targeted remediation within 8 weeks of report or triage.
  • Low (CVSS below 4.0): targeted remediation within 25 weeks of report or triage.

See also the Monolyn Labs Security Policy and security.txt.

What to include in a support request

  • Jira site URL
  • project key
  • board id or board name, if known
  • environment and app version, if known
  • steps to reproduce
  • screenshots or screen recording, if available
  • what you expected to happen versus what actually happened

Common issues

No Scrum boards found

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

Health shows “No signal”

This usually means the sprint has no assigned issues, no detected assignees, or insufficient data to derive capacity.

Health shows “Counts”

The selected board’s estimation method could not be read. Configure Story Points or a time-based estimate field on the board, then reload the page.

Utilization is blank

Confirm that the sprint has estimated issues, at least one detected assignee, and a non-empty capacity setting.

Recent scope change or deployment

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

Known limitations

  • Scrum boards only. Kanban boards are not supported.
  • The app focuses on the next three sprints.
  • Best results depend on issues being estimated and assigned.

Data, privacy, and deletion

Sprint Canvas stores only project-level configuration in Forge Storage, such as the selected board and capacity settings. It does not persist issue descriptions, comments, or attachments, and it does not send Jira data to third-party external services.

Reference links