StoryScale docs
Permissions and data handling.
StoryScale is designed as a Jira-first Forge app with explicit human control over write-back.
Jira Scopes
read:jira-workRead Jira issues, fields, and work data needed for import and readiness checks.
read:board-scope:jira-softwareRead Jira Software board context for sprint-based imports.
read:sprint:jira-softwareList active and future sprints for the selected board/project.
read:issue-details:jiraRead issue details required for estimation and readiness review.
read:jql:jiraRun bounded JQL searches selected by the user.
write:jira-workUpdate Story Points only after explicit publish confirmation.
storage:appSave session snapshots and resumable estimation state in Forge Storage.
Stored Session Data
StoryScale stores session snapshots scoped by cloud, project, and board. The saved data is intended to support review and resume workflows: session id, source label, issue keys, ranking state, estimate table, timestamps, and summarized issue metadata.
StoryScale does not use an external estimation backend in the Core version.
Data Boundaries
- No automatic changes to issue summary, description, status, comments, or assignee.
- No publishing of historical anchor stories.
- No write-back without user confirmation.
- No external AI service calls in the Core installable version.