Admin & Installation Guide
Audience: Jira Administrators · Platform: Atlassian Forge · Deployment: Jira Cloud
Overview
This guide covers installation, configuration, and management of SprintINSite (Jira Points Tracker) for Jira Cloud administrators.
System Requirements
- Jira Version: Jira Cloud (required)
- Board Type: Scrum boards (team-managed or company-managed)
- Active Sprint: At least one active sprint with story points assigned to issues
Installation from Marketplace
This is the recommended installation method for most teams:
- Go to Jira Settings then Apps then Find new apps
- Search for "SprintINSite" or "Jira Points Tracker"
- Click Install
- Grant the requested permissions when prompted
- The app will appear in all Scrum projects automatically as a project page tab
App Permissions
SprintINSite requires the following read-only OAuth scopes. The app does not create, modify, or delete any Jira data.
- storage:app — Store baseline snapshots for scope change tracking
- read:jira-work — Read issues and worklogs
- read:project:jira — Access project metadata
- read:issue-details:jira — Read issue fields including story points
- read:jql:jira — Execute JQL queries for sprint data
- read:board-scope:jira-software — Access board configuration
- read:sprint:jira-software — Read sprint data
- read:jira-user — Read user information for team capacity display
Data Storage
SprintINSite stores baseline data using the Forge Storage API. Baselines are scoped per project and sprint, and are used to track scope changes throughout a sprint. The storage key format is:
sprintBaseline:v2:{projectKey}:{sprintId}
The detected story points field ID is also cached for performance using the key spFieldId:v1.
All data remains within the Atlassian infrastructure. No external API calls are made and no user data leaves the Atlassian platform.
Security Considerations
- The app only reads Jira data — it has no write permissions
- Baseline data is stored in Forge Storage, isolated per app installation
- No external API calls are made
- No user data leaves Atlassian infrastructure
- All permissions are read-only: no issue creation or modification, no user management, and no project configuration changes
Upgrading
When a new version of SprintINSite is published to the Atlassian Marketplace, updates are applied automatically to all installations. No manual action is required from administrators.
Uninstallation
To remove SprintINSite from your Jira instance:
- Go to Jira Settings then Apps then Manage apps
- Find SprintINSite in the list of installed apps
- Click Uninstall
Note: Storage data (baselines) persists after uninstall in Forge Storage. If you reinstall the app, previous baselines will still be available.
Troubleshooting
"No Scrum-capable board found"
The project only has Kanban boards. SprintINSite requires Scrum boards. Create a Scrum board in the project or use the app in a different project that has one.
"No active sprint found"
No sprint is currently active in the project. Go to the Backlog, start a sprint, then return to the app.
App tab not appearing in project navigation
SprintINSite appears as a project page in Scrum projects. Check that the project uses a Scrum board type and that the app installation completed successfully in Jira Settings > Apps > Manage apps.
Error loading data
This is typically caused by network issues or permission problems. Verify that the user has project access permissions and that the board has issues with story points assigned. Click the Refresh button to retry.
Supported Board Types
- Company-managed Scrum boards (type "scrum") — Fully supported
- Team-managed Scrum boards (type "simple") — Fully supported
- Kanban boards — Not supported (requires sprints)
Support
For technical support, bug reports, or feature requests, contact us at support@sprintinsite.com.
For user-facing documentation, see the User Documentation and Quick Start Guide.
Version History
Version 1.0 (January 2026) — Initial release.