Site settings for Jira admins

Jira administrators get a site wide screen: the default every project inherits, every board on the site in one list, and how much Capacity Compass is actually being used.

Before you begin: You need the global Administer Jira permission. This screen is not visible to anyone else.

Open site settings

1. In Jira, go to Settings then Apps.
2. Select Capacity Planner.

Three sections: Manage availability, Default visibility, and Usage.

Default visibility

The rule applied to every project that has not set its own, and to every board nobody has switched by hand.

1. Select Default visibility.
2. Choose an option.
3. Check the line beneath, which states how many boards the change would move.
4. Select Save.

The count comes from the same calculation the save uses, so what it predicts is what happens.

Boards somebody has set by hand keep their own setting and are not moved. The same line says how many boards override the policy.

On a site with more boards than one read can enumerate, Capacity Compass cannot state the size of the change and saving is unavailable until it can. You cannot consent to a change whose blast radius is unknown.

Manage availability

Every board on the site, with its project, its activity, and whether it is enabled. The heading reads, for example, 14 of 22 boards enabled.

Change one board

Use the toggle in the board's row. If the board has plans, Capacity Compass asks you to confirm first.

Change several at once

1. Select the checkbox on each board you want to change.
2. Select Enable or Disable in the bar that appears.

Selection covers the page you are looking at. Selecting across pages would let one click move boards you never saw.

Return a board to the default

A board that has been set by hand shows a way to follow the site policy again. Use it when you want that board to inherit the default instead of keeping its own setting.

Find a board

Use the search field to search boards or projects. On a very large site the list is a prefix rather than everything, and Capacity Compass says so. Search for a specific board in that case.

Usage

Where Capacity Compass has actually landed: projects, how many boards each has enabled, how many plans exist, and when each was last active.

This is a rollout view. It answers where the app is being used and how many projects a usage limit would need to cover.

It is not a performance view. There are no delivery figures here, by design.

How the layers interact

1. A board someone has explicitly enabled or disabled keeps that setting.
2. Otherwise the board follows the site default.

Explicit choices always win. Changing the site default never overrides a decision someone made by hand.