What Capacity Compass reads from Jira

What Capacity Compass reads from Jira, what it stores, and what it never touches. Useful before approving the app, and when explaining it to a security reviewer.

The short version

Capacity Compass never writes to Jira. It holds no Jira write permission of any kind. It cannot create, edit, assign, transition, comment on, or delete anything in your Jira site, and this is enforced by the permissions it requests rather than by its own code.

Everything Capacity Compass produces, such as plans, hours, and activities, is stored by the app. Jira is a source it reads from.

What it reads

Jira data	Used for
Boards	Listing which boards can be planned, and telling Scrum from Kanban
Sprints	Sprint names, dates, and state, which set the planning window
Projects	Knowing which project you are in and listing projects in the admin usage view
Users	Names and avatars when searching for people to add to a plan
Issues in the sprint	Key, summary, type, status, assignee, and estimate, to work out assigned load
Fields and field configuration	Letting you choose which field holds estimates and which holds logged time
Worklogs or a time field	Comparing logged time against planned time. Optional
Your permissions	Checking whether you may change settings or board availability

Issues are read for the sprint being planned. Capacity Compass does not read your whole Jira backlog.

The permissions it requests

All eight are read permissions. There is no write permission in the list.

Permission	Why
`read:board-scope:jira-software`	Read boards
`read:sprint:jira-software`	Read sprints and their dates
`read:project:jira`	Read project details
`read:jira-user`	Find people to add to a plan
`read:jira-work`	Read issues in the sprint
`read:field:jira`	List fields you can choose as an estimate source
`read:field-configuration:jira`	Understand how those fields are configured
`read:permission:jira`	Check whether you may change settings

What it stores

Stored inside Atlassian's infrastructure, in a database belonging to your site's installation. Each Jira site has its own, and no data is shared between customers.

Stored	Contents
Plans	Plan name, the sprint it covers, and its window
Plan members	Jira account identifiers with their capacity hours for that plan
Activities and attendance	Meeting names, hours, and who attends
Plan settings	Estimate field, conversion, actual time source, hours per day
Board settings	Scales, default hours, field choices, standing meetings
Board availability	Which boards are enabled, and the site default
Sprint snapshots	Capacity and outcome captured at sprint start and close, used by Tracking

Personal data is limited to Jira account identifiers and the capacity figures attached to them. Capacity Compass does not store issue content, comments, or attachments.

What it never does

Create, edit, or delete Jira issues
Assign or reassign work
Transition issues or change workflow state
Add comments, labels, or attachments
Change Jira project or board configuration
Log time on your behalf
Send your data outside Atlassian's infrastructure

Deleting a plan removes the plan and its capacity setup. Jira is untouched.

Who can see what

Capacity Compass does not add a permission layer of its own. Someone who cannot see a Jira project cannot see its plans.

Within a project, anyone who can view it can read plans and report their own availability. Changing plans, settings, and board availability requires Administer projects. Site settings require Administer Jira.

Permission is checked on the server for every change, not only in the interface, so hiding a button is not what enforces it.

Availability reporting is visible

When someone reports their own hours, the figure and the time they answered are visible to whoever runs the plan. The check-in screen says so while they are filling it in.

Uninstalling

Removing the app removes its stored data along with the installation. Since nothing was written to Jira, there is nothing left behind in your projects, boards, or issues.